Windows AMSI.DLL Image Load by Uncommon Process Paths

Alerts when Amsi.dll is loaded by processes outside common Windows binaries and directories.

FreeReviewedSigma · Low · v5
Product
windows
Category
image_load
Author
frack113 (SigmaHQ), DRL 1.1
Published
2023-03-12
Updated
2026-07-31

ATT&CK techniques

Impact
  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

What it detects

This rule flags Windows image loads where the loaded module ends with \amsi.dll and the loading process image path does not match common system or known benign locations. Attackers may load or proxy AMSI components to interfere with script and content scanning, making unusual load locations relevant to impact-focused hunting. The detection relies on image load telemetry containing Image and ImageLoaded fields to match \amsi.dll and apply exclusion filters for specific executable paths and directories.

Related detections9 linkedT1490 — drag to rearrange
Malicious Volume Shadow Copy Deletion for Ransomware Recovery Inhibition
Malicious Volume Shadow Copy Deletion via wmic and vssadmin (via process_creation)
Malicious System Recovery Inhibition via bcdedit and vssadmin in Mallox
Malicious Shadow Copy Deletion via WMIC via Process Creation (via process_creation)
Suspicious Anti-Recovery Zeroing via fsutil setZeroData (via process_creation)
Malicious Shadow Copy Removal via WMI PowerShell
Malicious Volume Shadow Copy Deletion via vssadmin
Malicious Inhibit System Recovery via Shadow Copy and Boot Config Tampering (via process_creation)
Malicious Recovery Disablement via Bcdedit RecoveryEnabled No
Windows AMSI.DLL Image Load by Uncommon Process Paths
Pivot detection · T1490 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. v1
    No changelog recorded for this version.2026-07-30

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