ShadowHammer Embedded Malicious Code in ASUS Live Update
CVE-2025-59374 documents the ShadowHammer supply-chain compromise affecting certain ASUS Live Update client builds distributed during 2018–2019. Unauthorized modifications embedded malicious code in otherwise trusted update software. The code evaluated device-specific targeting conditions and caused unintended actions only on systems that both installed a compromised build and met those conditions. The issue is classified as CWE-506, Embedded Malicious Code. ASUS Live Update is unsupported, and no currently supported ASUS products are affected.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
On selectively targeted systems running a trojanized ASUS Live Update build, the embedded code enabled attackers to cause unintended actions in the context of the trusted update client. This could facilitate malware deployment or follow-on compromise of targeted endpoints. The original supply-chain operation selectively targeted a limited set of devices rather than all installations of the affected client.
If you can’t patch tonight, do this now.
Identify endpoints retaining ASUS Live Update, especially legacy installations, and remove the client where it is not required. Restrict software-update mechanisms to validated, vendor-supported tooling; verify software provenance and code-signing integrity; and conduct endpoint investigation and integrity validation for systems exposed during the affected distribution period. Replace unsupported update tooling with supported alternatives.
Patch, then assume compromise.
Remove or discontinue use of the unsupported ASUS Live Update client. For historical affected deployments where the client must remain present, ASUS addressed the compromised-update issue in Live Update version 3.6.8 and later; upgrade to a non-compromised version where operationally feasible. Review systems that may have installed affected builds for signs of compromise and rebuild or remediate systems for which integrity cannot be established.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
75 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.