2018 · J - Information and communication · Supply-chain attack: trojanised, fraudulently signed game executables
Analysed 2026-11-07 by Hermes
Open this case in the tool →Supply-chain attack: trojanised, fraudulently signed game executables
Expertise to Execution
Evidence coverage: 3/6 stages, weight 15/60
Decisive stage: entry (clearest evidence) · Alternative: Expertise to Leadership
(1) The expectation at any game publisher is that its production/build environment and code-signing certificate stay out of attacker reach and that binaries are verified before release to players, because the signed installer is exactly what the user base is told to trust - here a Southeast/East Asian developer group distributing popular online titles. (2) In practice, from July 2018 APT41 injected the CRACKSHOT backdoor into the developers' legitimate executables and the trojanised files went out signed with the organisations' own code-signing certificates, which FireEye/Mandiant assess as most likely indicating access to the production environment; none of the developers noticed - the compromise was disclosed by IT-security companies, and as late as 11 March 2019 Electronics Extreme was still distributing the trojanised Infestation build after ESET had tried to inform it several times through various channels since early February without apparent success, leaving tens or hundreds of thousands of mostly Thai, Filipino and Taiwanese users running the backdoored binaries. (3) The classification rests on the entry stage (clearest evidence; the detection gap points the same way): the remedies - segmenting the build environment from attacker-reachable systems, restricting signing-key custody, and integrity-checking release binaries - sit with technical specialists, and the chain broke in operations and architecture, since the injection passed through the victim's own build, signing and release chain; the sources document no policy, standard or leadership decision behind the missing protection, so this is not a Strategy-to-Execution or Strategy-to-Leadership gap, and the initial access vector itself is undisclosed and not load-bearing. The response stage carries a secondary Expertise to Leadership pattern: an external expert warning (ESET's report) that found no owner able to act; it is contributing and partly inferred, so the entry stage stays decisive. (4) RM29 (Expertise to Execution lens): the breach ran through the developers' own production environment - malicious code injected into legitimate executables and signed with the organisations' own certificates - so the specialist-known controls around build pipelines and signing infrastructure were never realised in the architecture (causal role: Enabling). RM34 (Expertise to Execution lens): no developer detected the trojanisation itself; it was found by ESET, Kaspersky and FireEye telemetry months later, showing monitoring and release-integrity checking were insufficiently configured or staffed to spot injected code in their own signed binaries (causal role: Obscuring). RM07 (Expertise to Execution lens): ESET's findings could not be made actionable inside the organisation - repeated contact attempts since early February 2019 had no apparent effect and the trojanised build stayed in distribution, so the external expert evidence never became visible or credible to anyone able to act on it (causal role: Perpetuating).
RM29 — Secure-development / non-production exposureRM34 — Monitoring / detection / alert-handling gapRM07 — Risk signal / escalation suppressionCase file names no organisation (receiver_name absent): victim named descriptively from the row's description and the vendor reporting, which identify several East/SE Asian developers/distributors including Electronics Extreme (Thailand, game Infestation) and the PointBlank distributor. Country left null: the case file gives receiver_country as two regions (Southeast Asia; Eastern Asia), not a country, and this is a campaign across several companies (affected users concentrated in Thailand, the Philippines and Taiwan). Year 2018 from eurepoc_extra.start_date (01.07.2018). The row's source_url (mandiant.com PDF) returns an HTML bot-block page, not the report; the same FireEye/Mandiant report (Double Dragon: APT41, A Dual Espionage and Cyber Crime Operation) was opened as the Google-hosted PDF cited here. ESET's original WeLiveSecurity article (welivesecurity.com/2019-03-11/...) 404s at its original URL and the Wayback Machine refused requests from this host, so ESET's own press-release copy of the same analysis is cited instead. Attribution is technical (IT-security community, per case file); no official/government attribution found for this specific supply-chain incident. FireEye attributes the July 2018 compromises to APT41 as Confirmed (Table 1 of the report). Only public reporting was used, per the research boundaries; unattended run: no consent-requiring action was needed.