Automation · API / MCP 中文

Group profile · G0126

Higaisa

Higaisa is a threat group suspected to have South Korean origins. Higaisa has targeted government, public, and trade organizations in North Korea; however, they have also carried out attacks in China, Japan, Russia, Poland, and other nations. Higaisa was first disclosed in early 2019 but is assessed to have operated as early as 2009.

ATT&CK G0126 Confidence High · 100 Source src_mitre_attck_enterprise Status active
All2021

Showing 2021 citations only; facet pages stay out of the index and canonicalise to the profile.

Higaisa is a threat group suspected to have South Korean origins. Higaisa has targeted government, public, and trade organizations in North Korea; however, they have also carried out attacks in China, Japan, Russia, Poland, and other nations. Higaisa was first disclosed in early 2019 but is assessed to have operated as early as 2009.123

  1. Malwarebytes Higaisa 2020
  2. Zscaler Higaisa 2020
  3. PTSecurity Higaisa 2020

Claims and citations

Every claim comes from a writer; provenance is the writer's assertion, not a review verdict from this directory. Validity reads by citation year.

predicateobjectValidConf.Evidence
uses_techniquetech_t1059.0052021 → …100src_mitre_attck_enterprise
uses_techniquetech_t11062021 → …100src_mitre_attck_enterprise
uses_techniquetech_t10412021 → …100src_mitre_attck_enterprise
uses_techniquetech_t1574.0012021 → …100src_mitre_attck_enterprise
uses_techniquetech_t11242021 → …100src_mitre_attck_enterprise
uses_techniquetech_t1090.0012021 → …100src_mitre_attck_enterprise
uses_techniquetech_t1204.0022021 → …100src_mitre_attck_enterprise
uses_techniquetech_t1027.0132021 → …100src_mitre_attck_enterprise
uses_techniquetech_t1053.0052021 → …100src_mitre_attck_enterprise
uses_techniquetech_t10822021 → …100src_mitre_attck_enterprise
uses_techniquetech_t1566.0012021 → …100src_mitre_attck_enterprise
uses_techniquetech_t1071.0012021 → …100src_mitre_attck_enterprise
uses_techniquetech_t1001.0032021 → …100src_mitre_attck_enterprise
uses_techniquetech_t12032021 → …100src_mitre_attck_enterprise
uses_techniquetech_t10292021 → …100src_mitre_attck_enterprise
uses_techniquetech_t1059.0072021 → …100src_mitre_attck_enterprise
uses_techniquetech_t1027.0012021 → …100src_mitre_attck_enterprise
uses_techniquetech_t1027.0152021 → …100src_mitre_attck_enterprise
uses_techniquetech_t12202021 → …100src_mitre_attck_enterprise
uses_techniquetech_t1564.0032021 → …100src_mitre_attck_enterprise
uses_techniquetech_t1573.0012021 → …100src_mitre_attck_enterprise
uses_techniquetech_t16802021 → …100src_mitre_attck_enterprise
uses_techniquetech_t1547.0012021 → …100src_mitre_attck_enterprise
uses_techniquetech_t10572021 → …100src_mitre_attck_enterprise
uses_techniquetech_t1036.0042021 → …100src_mitre_attck_enterprise
uses_techniquetech_t10162021 → …100src_mitre_attck_enterprise
uses_techniquetech_t1059.0032021 → …100src_mitre_attck_enterprise
uses_techniquetech_t11402021 → …100src_mitre_attck_enterprise

Technique use

ATT&CKTechniqueplatforms
T1001.003Protocol or Service Impersonation—
T1016System Network Configuration Discovery—
T1027.001Binary Padding—
T1027.013Encrypted/Encoded File—
T1027.015Compression—
T1029Scheduled Transfer—
T1036.004Masquerade Task or Service—
T1041Exfiltration Over C2 Channel—
T1053.005Scheduled Task—
T1057Process Discovery—
T1059.003Windows Command Shell—
T1059.005Visual Basic—
T1059.007JavaScript—
T1071.001Web Protocols—
T1082System Information Discovery—
T1090.001Internal Proxy—
T1106Native API—
T1124System Time Discovery—
T1140Deobfuscate/Decode Files or Information—
T1203Exploitation for Client Execution—
T1204.002Malicious File—
T1220XSL Script Processing—
T1547.001Registry Run Keys / Startup Folder—
T1564.003Hidden Window—
T1566.001Spearphishing Attachment—
T1573.001Symmetric Cryptography—
T1574.001DLL—
T1680Local Storage Discovery—

Aliases

Higaisa

Reading and review

Records are auto-ingested and not human-reviewed. Confidence is the writer's 0–100 value; bands split at ≥80 / 50–79 / <50 into high / medium / low. The four trust axes (synthetic, lifecycle, band, source count) stay separate and never merge into one score.

Corrections