← Breach analysis by the Dual Vulnerabilities framework

SK defense subcontractor ISR-manual data theft (suspected North Korea, 2024)

2024 · South Korea · M - Professional, scientific and technical activities · State-linked data theft via supply-chain intrusion

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

State-linked data theft via supply-chain intrusion

Dual vulnerability type

Strategy to Execution

Evidence coverage: 3/6 stages, weight 18/60

Decisive stage: entry (clearest evidence) · Alternative: Strategy to Leadership

Why this classification

(1) The victim - an unnamed small firm producing operation and maintenance manuals for South Korean military equipment, including the Baekdu and Geumgang reconnaissance aircraft, for a prime contractor working with DAPA - sat inside a doctrinal defense technology-protection regime: government joint integrated protection surveys, DAPA vulnerability-diagnosis programmes and government security-staffing guidelines existed before the intrusion. (2) In practice that regime stopped at the prime-contractor boundary: DAPA data reported in October 2024 showed defense contractors are exempt from the government cyber-security surveys, security employment standards are recommended rather than enforced, even the largest primes devote only 0.6 percent of defense staff to security, and general partner firms have not even aggregated security-staffing data; officials and the public-private defense-intrusion council both described attackers deliberately bypassing hardened primes and routing through low-security subcontractors. In August 2024 this subcontractor was breached (attributed by DAPA to the North Korean military) and O&M plus technical data on the two ISR aircraft, including recent upgrades, were exfiltrated - with DAPA conceding it could not tell whether core technology files had also gone. (3) The decisive gap is at the entry/exposure (pre-breach) stage, is doctrinal in origin and broke in execution: the protective expectations existed as formal artefacts but were content- and organizationally unhinged from the operational reality of the supply-chain tier that actually held the crown-jewel data - formal strategy never translated into IT reality where it mattered. The entry vector itself is undisclosed and is not load-bearing; the classification does not rest on the attacker's technique. A secondary pattern of Strategy to Leadership (DAPA minimizing the incident, leaving the core-technology question open) sits in the response stage, but it is the state customer's conduct, it is only contributing, and the pre-breach condition prevails. (4) RM13 (Strategy to Execution lens): supplier-security requirements, contracts and monitoring for the defense supply chain did not translate into controlled third-party operation - firms holding classified O&M data for national ISR assets were left outside government assessment and monitoring while remaining on the data path (causal role: Enabling). RM08 (Strategy to Execution lens): the strategic protection requirements were never backed by implementable capacity at subcontractor scale - security staffing was negligible even at primes, partner firms could not even show aggregated staffing data, and support programmes reached only selected core partners (sector-level survey evidence, not firm records) (causal role: Enabling). RM33 (Strategy to Execution lens): logging and evidence-preservation expectations were not realized in systems the authorities could rely on - the exfiltration scope stayed undetermined, with DAPA unable to say whether core technology had been taken (causal role: Obscuring).

Evidence by stage

Risk markers

Sources

Notes

Case file source_url hankyung.com/article/202408078398i is the related K2 tank insider-leak case (engineers referred to prosecution for moving designs to a competitor) reported in the same August 2024 news cycle, not the subcontractor hacking itself; the hacking narrative rests on the Dong-A Ilbo, Korea Herald and BleepingComputer articles cited. The victim firm was never named by the authorities and its entry vector was never disclosed; the classification rests on the pre-breach structural condition and the undetermined exfiltration scope, not on an entry technique. The response-stage gap rests on DAPA/state-authority statements and conduct (the data owner and customer); the firm itself made no public statement. RM08 rests on sector-level evidence - the government joint integrated protection survey figures from DAPA data submitted to Rep. Lim Jong-deuk's office - not on the victim firm's own records. EuRepoC start_date 01.01.2024 reflects the dataset coding of the early-2024/summer-2024 reporting window; first public disclosure was media reports of 7-9 Aug 2024 with DAPA's attribution reported 8 Aug 2024. The April 2024 NPA announcement (Lazarus/Andariel/Kimsuky hit ~10 of 83 defense organizations from Oct 2022, none aware until the Jan-Feb 2024 joint police/DAPA/NIS inspection) is a prior sector-wide warning; it is not established that this firm belonged to that wave. Dong-A Ilbo adds that police traced the attacks by IP and confirmed investigations into further hacking attempts against other DAPA-related subcontractors. All cited URLs opened OK on 06-11-26 (check_result --links). Link check: hankyung.com blocks automated access (HTTP 403); the page was opened and read during research.