{
  "family": "shadowhammer",
  "sample_count": 1,
  "category": "backdoor",
  "description": "<h3>Executive Summary</h3>\nOperation ShadowHammer was a highly sophisticated Advanced Persistent Threat (APT) supply chain attack discovered in 2019, attributed to the Chinese state-sponsored group Barium (also known as APT41). The attackers successfully compromised the ASUS Live Update Utility, allowing them to push cryptographically signed, weaponized software updates to hundreds of thousands of ASUS computers globally. However, the malware's payload was designed to execute only on a highly specific, pre-determined list of target machines.\n\n<h3>Infection Vector and Technical Capabilities</h3>\nThe infection vector was a classic upstream supply chain compromise. The attackers breached ASUS's internal network, compromised their software build environment, and weaponized the legitimate `setup.exe` for the ASUS Live Update tool. Because the executable was signed with a legitimate ASUS digital certificate, it bypassed standard antivirus checks and was installed silently by the update utility.\n\nOnce installed, ShadowHammer demonstrated extreme precision and stealth:\n<ul>\n<li><strong>MAC Address Targeting:</strong> The weaponized update contained a hardcoded list of roughly 600 specific MAC addresses (hashed using MD5). Upon execution, the malware checked the victim's MAC address against this list.</li>\n<li><strong>Dormant vs. Active:</strong> If the MAC address did not match, the malware remained dormant, taking no malicious action to avoid raising suspicion. If the MAC address *did* match, it initiated a secondary stage.</li>\n<li><strong>Secondary Payload Delivery:</strong> For the targeted machines, the malware reached out to an attacker-controlled C2 server (often disguised as a legitimate ASUS domain) to download a secondary, memory-resident backdoor, providing the APT group with full remote access to the high-value target.</li>\n</ul>\n\n<h3>Threat Assessment</h3>\nShadowHammer is a masterclass in supply chain compromise and targeted espionage. The fact that the attackers could compromise a major hardware vendor's update infrastructure, sign the malware with legitimate certificates, and deploy it to half a million machines just to target 600 specific individuals highlights the extreme capability and patience of state-sponsored APT groups.\n\n<h3>Incident Response and Remediation</h3>\n<ul>\n<li><strong>Update the Update Utility:</strong> The immediate remediation for the general public was to update the ASUS Live Update utility to a new version (which included enhanced security checks) and run a diagnostic tool provided by ASUS to determine if the specific machine was targeted.</li>\n<li><strong>Targeted Forensics:</strong> For organizations that discovered their MAC addresses were on the target list, a \"break-glass\" incident response protocol was required. This necessitated a complete forensic investigation of the endpoint and the surrounding network to identify the secondary backdoors deployed by APT41 and the extent of the data exfiltration.</li>\n<li><strong>Zero-Trust Architecture:</strong> ShadowHammer demonstrates that even digitally signed software from trusted vendors cannot be implicitly trusted. Organizations must adopt Zero-Trust principles, heavily monitoring endpoint behavior (EDR) rather than relying solely on signature-based or certificate-based trust models.</li>\n</ul>",
  "cta": "Published by the SystemHelpdesk team.",
  "aliases": [
    "APT.ShadowHammer",
    "Trojan.ASUSUpdate",
    "Backdoor.Barium",
    "APT41"
  ],
  "enrichment_level": "expert-seo",
  "faq": [
    {
      "@type": "Question",
      "name": "What is Shadowhammer and what threat category does it belong to?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Shadowhammer is classified as a Backdoor. Documented across security telemetry, it is engineered to execute unauthorized operations, establish persistent footholds on target endpoints, and facilitate malicious campaigns targeting enterprise and individual environments."
      }
    },
    {
      "@type": "Question",
      "name": "How does Shadowhammer establish persistence and evade defensive controls?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Shadowhammer typically establishes persistence through registry run keys, scheduled tasks, or service installations, while evading signature-based antivirus solutions through code obfuscation, memory injection, or anti-analysis sandbox checks."
      }
    },
    {
      "@type": "Question",
      "name": "What are the essential incident response steps for mitigating a Shadowhammer compromise?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Security teams responding to Shadowhammer should immediately isolate affected endpoints from the network, perform memory triage to capture volatile forensic artifacts, audit registry and startup persistence mechanisms, revoke exposed user credentials, and restore systems from verified, clean backups."
      }
    },
    {
      "@type": "Question",
      "name": "What remote administrative and surveillance capabilities does APT.ShadowHammer provide to threat actors?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "As an interactive backdoor and remote access tool, APT.ShadowHammer grants operators comprehensive control over the victim host. Common surveillance and management modules include real-time keystroke logging, desktop screen capture, remote VNC streaming, webcam and audio recording, arbitrary shell command execution, reverse proxy pivoting, and bidirectional file transfer capabilities."
      }
    },
    {
      "@type": "Question",
      "name": "How does APT.ShadowHammer traverse firewalls and sustain resilient command-and-control (C2) connections?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "APT.ShadowHammer establishes persistent outbound TCP or TLS connections back to threat actor infrastructure, effectively bypassing inbound firewall filtering. To maintain connection resilience against IP takedowns, variants frequently employ dynamic DNS services, fallback command servers, encrypted dead-drop resolvers on social platforms, or DNS over HTTPS (DoH) querying."
      }
    }
  ],
  "faq_count": 5,
  "mitre_attack": [
    "T1195.002",
    "T1553.002",
    "T1016",
    "T1105"
  ],
  "cisa_advisory": null,
  "last_updated": "2026-10-15",
  "type": "APT / Supply Chain Attack",
  "target_industries": [
    "Global / Opportunistic"
  ],
  "motivation": "Opportunistic",
  "threat_actors": [
    "Unknown / Cybercriminal"
  ],
  "target_geographies": [
    "Global"
  ],
  "attack_stage": [
    "persistence",
    "command_and_control",
    "remote_access"
  ],
  "ecosystem": [
    "windows_pe"
  ],
  "is_emerging": false,
  "mitre_attack_detail": [
    {
      "id": "T1195.002",
      "name": "Compromise Software Supply Chain",
      "tactic": "initial-access"
    },
    {
      "id": "T1553.002",
      "name": "Code Signing",
      "tactic": "defense-evasion"
    },
    {
      "id": "T1016",
      "name": "System Network Configuration Discovery",
      "tactic": "Discovery"
    },
    {
      "id": "T1105",
      "name": "Ingress Tool Transfer",
      "tactic": "Command and Control"
    }
  ],
  "containment_steps": [
    "Immediately isolate the compromised host from internal LAN and WAN environments to cut off interactive remote shell sessions established by Shadowhammer.",
    "Inspect active socket listeners and outbound established network connections ('netstat -ano') to identify and sever covert TCP/UDP channels used by Shadowhammer.",
    "Scan Windows Services, Scheduled Tasks, and Startup folders to locate and eliminate persistent backdoor listeners configured by Shadowhammer.",
    "Invalidate all active VPN profiles, local administrator credentials, and session tokens that may have been harvested by the Shadowhammer operator.",
    "Re-image the affected host using a validated golden image prior to reconnecting it to enterprise network segments."
  ],
  "what_to_avoid": [
    "Do not attempt to interact with or send messages through the Shadowhammer remote terminal, as this alerts the attacker and may cause them to execute destructive anti-forensic commands.",
    "Avoid relying solely on static file signatures, as Shadowhammer payloads frequently execute reflectively in memory without writing binaries to disk."
  ],
  "target_platforms": [
    "Windows 11",
    "Windows 10",
    "Windows Server 2022",
    "Windows Server 2019"
  ]
}