Malicious AMSI Bypass via AmsiUtils amsiInitFailed Manipulation

PremiumReviewedSigma · High · v1
Product
windows
Category
ps_script
Author
HuntRule
Published
2026-05-23
Updated
2026-08-28

ATT&CK techniques

Execution
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects PowerShell script content that disables the Antimalware Scan Interface by reflecting into System.Management.Automation.AmsiUtils and setting the amsiInitFailed field to true. This in-memory AMSI bypass was observed during React2Shell CVE-2025-55182 exploitation to blind endpoint scanning before executing follow-on payloads.

Related detections9 linkedT1059.001 — drag to rearrange
Suspicious Windows Defender Exclusion Added via PowerShell Add-MpPreference
Suspicious PowerShell AMSI or ETW Tampering
Custom Cobalt Strike Command Execution
Malicious Windows Defender Real-Time Monitoring Disabled via PowerShell
Suspicious node.exe Execution Spawned by PowerShell
Suspicious PowerShell Spawned by mshta.exe in FakeSG Chain (via process_creation)
Suspicious Encoded PowerShell Using Base64 Stream Decompression Routines (via process_creation)
Malicious IIS Worker Process Spawning Command Shell for Webshell Reconnaissance (via process_creation)
Suspicious PowerShell Spawned by Windows Script Host during Scarlet Goldfinch Infection (via process_creation)
Malicious AMSI Bypass via AmsiUtils amsiInitFailed Manipulation
Pivot detection · T1059.001 · 9 related

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