← Breach analysis by the Dual Vulnerabilities framework

ShadowHammer ASUS Live Update backdoor (Barium/APT41, 2018)

2018 · C - Manufacturing · Supply-chain attack via trojanized automatic software updates

Analysed 2026-11-06 by Hermes

Open this case in the tool →

What happened

Supply-chain attack via trojanized automatic software updates

Dual vulnerability type

Expertise to Execution

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

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

Why this classification

(1) ASUS is the world's fifth-largest PC vendor and its Live Update channel is the carrier of customer trust: the expectation that the build environment, code-signing keys and every published installer are protected and verified is established specialist practice, and even a user can in principle hash-verify what the server sends. (2) In practice the software supply chain itself was breached: the attackers reached the build environment (Kaspersky concluded they had access to the source or injected malware at compilation time), trojanized Live Update binaries were signed with legitimate ASUSTeK code-signing certificates and pushed from the official update servers from June to November 2018; the implant stayed silent on non-target machines, Kaspersky first found it on 29-01-2019, and ASUS itself never reported detecting it. How the attackers first entered ASUS's network was never disclosed - the entry technique is not what is load-bearing here; what is, is that the vendor's own signing and publication architecture did not catch tampered, re-signed binaries for about five months. (3) The remedy sat with technical specialists - secure build and signing pipelines, controlled key custody, pre-publication integrity checks, monitoring of update artifacts - and no source shows a leadership decision that deferred or defunded it; the chain broke where doctrine meets architecture, in execution. Material origin plus execution break makes this Expertise to Execution, and the entry stage is the case's only load-bearing gap. A secondary pattern is visible in the response stage: ASUS stayed silent for two months after being notified and then downplayed the scope when its own partner's disclosure forced a statement - a Strategy to Leadership reading - but that stage is contributing-weighted and ASUS's 'very small number' framing partly matches the small set of implanted targets, so it does not outrank the documented pipeline gap. RM29 (Expertise to Execution lens): the developers' and publishers' known secure-practice rules for the software delivery pipeline were not applied - a compromised linker/build path let attackers compile the backdoor into the signed updater and let the signed trojanized files pass publication (causal role: Enabling). RM34 (Expertise to Execution lens): the tooling and monitoring that could flag an anomalous updater were present in the ecosystem - users uploaded suspicious files to VirusTotal and complained as early as June-September 2018, and Kaspersky's telemetry found the trojanized signed binary - but ASUS's own detection environment never raised on five months of tampered updates on its own servers (causal role: Obscuring). RM38 (Expertise to Execution lens): after notification, scoping and eradication stayed incomplete - a newer file was still being signed with a compromised certificate when Kaspersky flagged it again during the joint investigation, and the total number of affected users was never established (causal role: Amplifying).

Evidence by stage

Risk markers

Sources

Notes

Data quality: the case file carries no receiver_name and the workbook victim field holds the operation name 'Operation Shadow Hammer'; the description - 'Barium inserted backdoors into automatic updates for ASUS lAPT ops' - shows the victim organisation whose lifecycle is assessed is ASUS (Taiwan), with its Live Update end users as downstream targets (receiver_category 'End user(s) / specially protected groups'). Country left null because the case file records receiver_country as 'Global (region)'. Year 2018 from start_date 01.06.2018 (the June-November 2018 distribution window in Kaspersky's report); public disclosure was March 2019. Sector taken from ASUS, the computer-hardware maker whose update infrastructure was breached. Attribution: the case file lists both Barium/APT41 and APT17 (Winnti umbrella); Kaspersky links the code to BARIUM/ShadowPad, and the 2020 DOJ indictment of Chinese nationals covers the ShadowHammer supply-chain attacks (BleepingComputer, the third source_url in the case file, is about APT41 tooling and that indictment, not the ASUS incident itself). The case file's 'about 5 Months' active period matches the June-November 2018 window. The ASUS press release cited by Dark Reading (asus.com/News/hqfgVUyZ6uyAyJe1) no longer opens - it redirects to the current news index - so the company's 26-03-2019 statement is cited from the TechTarget and Dark Reading articles instead. The 'one zero-day' in the case file concerns attacker-side exploit use in the wider campaign and is not load-bearing for the victim-side classification. Unattended run: no step required consent, none skipped.