← Breach analysis by the Dual Vulnerabilities framework

South Korea and allied targets espionage campaign (APT37, 2012)

2012 · O - Public administration and defence · Cyber espionage campaign (data theft, system hijacking)

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Cyber espionage campaign (data theft, system hijacking)

Dual vulnerability type

No DV evidenced

Alternative: none defensible

Why this classification

The row describes a perennial North Korean state espionage campaign (APT37/Reaper, active since at least 2012) against a diffuse set of mostly unnamed targets: South Korean government, military, defence-industrial, media, human-rights and defector organisations, plus entities in Japan, Vietnam and the Middle East. The entire documentation of the campaign - the FireEye/Mandiant special report that EuRepoC cites as source and attribution source, and the press coverage of its February 2018 publication - is written from the attacker's side: targeting, lure themes, infection vectors (spearphishing with malicious Hangul Word Processor and Office documents, strategic web compromises, torrent-distributed malware), exploited vulnerabilities including zero-days (CVE-2018-4878, CVE-2018-0802), C2 infrastructure and attribution artefacts. Nothing is documented about any victim organisation's own situation: no victim policy, strategy or standard is named (so no doctrinal origin can be evidenced), no expert warning or known remedy left unexecuted at a specific victim is recorded (so no material origin can be evidenced), and no stage of the lifecycle - entry, containment, detection, egress, recovery, response/disclosure - yields a victim-side gap. The incidents were disclosed by IT-security companies, not by victims, and the exploited zero-days by definition left no remediation window. This is a state-on-state, multi-organisation campaign of the kind the method spec treats as having no single victim organisation in the framework's sense: the reporting confirms impact (data theft, system compromise) only. Per the decision rule, DV-Type is Unknown (insufficient evidence of a victim-side mechanism at any lifecycle stage; atypical, attacker-side state operation); no DV-Type is forced from the attacker's techniques.

Sources

Notes

Diffuse multi-target campaign: no single victim organisation; victim named descriptively from receiver_category/receiver_subcategory. Country left null per method spec (multi-organisation, multi-country campaign: South Korea, Japan, Vietnam, Middle East region); Year 2012 is the eurepoc_extra start_date (campaign continued past the 2018 attribution disclosure). Sector set to O because the dominant and first-listed receiver categories are state institutions (government/ministries, military); the campaign in fact spans many sectors (transportation, health, telecom, finance, defence industry, advocacy, media). The case file's source_url (www2.fireeye.com PDF) no longer serves the report (returns an HTML stub); the cited web.archive.org snapshot of that exact PDF was opened and read during this task. Zero-days used by the actor (multiple, per eurepoc_extra) leave no remediation window, and the record contains no victim-side conditions, so no risk markers are coded. Searches for victim-side or government records (KISA/advisories, victim statements) around this campaign surfaced only further vendor threat reports; the Egyptian telecom angle reported in The National was denied by the named company and concerns an unnamed firm. Disclosure was by IT-security companies, not by victims.