Suspicious PowerShell AMSI Bypass via 8220 Gang Hadooken Loader

PremiumReviewedSigma · High · v1
Product
windows
Category
ps_script
Author
HuntRule
Published
2026-10-26
Updated
2026-10-26

ATT&CK techniques

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule detects PowerShell code that patches the Anti-Malware Scan Interface by reflectively accessing amsiInitFailed or the AmsiUtils type to disable in memory scanning. The 8220 gang uses an AMSI bypass before launching its CCleaner64.exe branded loader in the Hadooken campaign. Disabling AMSI is a common precursor to fileless payload execution and rarely appears in benign scripts.

Related detections9 linkedT1685 — drag to rearrange
Malicious Windows Defender Tampering via Set-MpPreference and Add-MpPreference (via ps_script)
Malicious Microsoft Defender Services Stopped via sc.exe
Suspicious Microsoft Defender Definitions Removed via MpCmdRun
Suspicious Defender Behavior Monitoring Disable via PowerShell (via process_creation)
Suspicious Windows Defender Real-Time Monitoring Disable (via process_creation)
Malicious Microsoft Defender Real-Time Monitoring Disabled via Set-MpPreference (via process_creation)
Suspicious Windows Defender Exclusion Added via PowerShell via Process Creation (via process_creation)
Malicious TCC AppleEvents Reset via Tccutil
Suspicious ESXi Management Agent Stop via vpxa init Script (via process_creation)
Suspicious PowerShell AMSI Bypass via 8220 Gang Hadooken Loader
Pivot detection · T1685 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.