Malicious PowerShell AMSI Bypass via AmsiInitFailed Command Line

PremiumReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
HuntRule
Published
2026-06-07
Updated
2026-08-28

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 the amsiInitFailed AMSI-bypass string in a PowerShell command line, a defense-evasion technique used after Citrix Bleed exploitation to disable script scanning before running the LockBit toolkit. Setting amsiInitFailed forces AMSI to skip inspection. Detecting the string exposes an active attempt to blind endpoint script scanning.

Related detections9 linkedT1685 — drag to rearrange
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)
Malicious ESXi Firewall Disable via esxcli (via process_creation)
Malicious ESXi Syslog Redirection to tmp via esxcli
Suspicious Windows Defender Exclusion Enumeration via reg query (via process_creation)
Malicious Windows Defender Exclusion Added via PowerShell (via process_creation)
Malicious BYOVD EDR Kill via Renamed GMER Driver by Agonizing Serpens
Malicious PowerShell AMSI Bypass via AmsiInitFailed Command Line
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.