How to Check for ASUS Live Update Backdoors and Update Affected Systems

Summary
Huntress outlines checks for the ASUS Live Update supply-chain attack, including searching for idx.ini and checking targeted MAC addresses, and recommends updating Live Update to version 3.6.8.
Key points
- Attackers compromised ASUS’s Live Update infrastructure between June and November 2018 and distributed backdoored updates.
- The backdoor checked whether a device was a target; Kaspersky estimated over one million hosts may have run a backdoored update, while about 600 were targeted for a second-stage payload.
- Huntress says the backdoored Setup.exe could leave an idx.ini file on systems that were not targeted; searching for the file can indicate that a backdoored update ran.
- ASUS and Kaspersky released diagnostic tools to check whether a computer’s MAC address was among the targeted addresses.
- ASUS urged users to update Live Update to version 3.6.8, which it said added security verification and stronger end-to-end encryption.
- Huntress observed that some older Live Update versions could fail to find the update, and reported not finding a manual installer at the time.
Article Details
- Defense Focus
- Identify systems that ran the backdoored ASUS Live Update and determine whether targeted systems received the second-stage payload.
- Detection Methods
- Search host file systems for idx.ini as an indicator that a backdoored update was executed.
- Use the ASUS or Kaspersky Lab diagnostic tools to compare a host's MAC address against the list of targeted addresses.
- Use the released list of targeted MAC addresses to check systems manually.
- Data Sources
- Host file-system artifacts
- Installed ASUS Live Update version
- Host MAC addresses
- Defensive Actions
- Update ASUS Live Update to version 3.6.8.
- Investigate systems running Live Update below version 3.6.8, including hosts that fail to find the update through the application.
- If a host matches a targeted MAC address or is otherwise identified as targeted, investigate it for the second-stage payload and seek incident-response assistance.
Indicators of compromise
| Type | Indicator | Context |
|---|---|---|
| URL | hxxp[:]//liveupdate01[.]asus[.]com/pub/ASUS/nb/Apps_for_Win8/LiveUpdate/Liveupdate_Test_VER365.zip | URL identified in the article as a malicious backdoored Live Update archive. |
| URL | hxxps[:]//liveupdate01s[.]asus[.]com/pub/ASUS/nb/Apps_for_Win8/LiveUpdate/Liveupdate_Test_VER359.zip | URL identified in the article as a malicious backdoored Live Update archive. |
| URL | hxxps[:]//liveupdate01s[.]asus[.]com/pub/ASUS/nb/Apps_for_Win8/LiveUpdate/Liveupdate_Test_VER360.zip | URL identified in the article as a malicious backdoored Live Update archive. |
| URL | hxxps[:]//liveupdate01s[.]asus[.]com/pub/ASUS/nb/Apps_for_Win8/LiveUpdate/Liveupdate_Test_VER362.zip | URL identified in the article as a malicious backdoored Live Update archive. |
MITRE ATT&CK
T1027 · Obfuscated Files or InformationThe backdoored Setup.exe contained an obfuscated shellcode payload.T1140 · Deobfuscate/Decode Files or InformationThe article reports that backdoored Setup.exe was modified to decrypt and run the attackers' payload.T1195.002 · Compromise Software Supply ChainAttackers compromised ASUS's automatic updating infrastructure and delivered backdoored updates through ASUS Live Update.
People
Vendors
AsusHomeBlogRapid Response: ASUS Live Update Attack (Operation ShadowHammer)HuntressPeriodically, a large scale cybersecurity issue requires “all hands on deck” from the Huntress Team (see WannaCry, Kaseya Cryptominer, GANDGRAB outbreak).KasperskyKaspersky Lab suggests that over a million hosts may have run a backdoored update.
