Windows Defender Windefend AMSI Detection (Event ID 1116)

Flags Windows Defender AMSI detections via windefend Event ID 1116 with SourceName set to AMSI.

FreeReviewedSigma · High · v2
Product
windows
Service
windefend
Author
Bhabesh Raj (SigmaHQ), DRL 1.1
Published
2020-09-14
Updated
2026-07-31

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 flags Windows Defender AMSI-triggered detections where the antimalware platform (AMSI) reports malware or potentially unwanted software via Event ID 1116. Such detections matter because AMSI is commonly used to identify malicious script or content during execution attempts. The rule relies on windefend telemetry carrying the EventID value and the AMSI SourceName.

Related detections9 linkedT1059 — drag to rearrange
AutoIt Script Execution via A3X Payload
Suspicious Python Execution via Renamed Synaptics Binary
MSBuild Executing Non-Project File or Remote Payload
Possible Ivanti Pulse Connect Secure Command Injection via License Keys-Status Endpoint (via webserver)
Possible Craft CMS RCE via Query-String CLI Option Injection
Possible Aspera Faspex Pre-Auth RCE via YAML Deserialization in package_relay (via webserver)
Possible Sitecore Pre-Auth RCE via Report.ashx Insecure Deserialization (via webserver)
Possible WatchGuard Pre-Auth RCE via agent login XML-RPC CVE-2022-26318
Possible Oracle Opera CGI Webshell Command Execution via operabin
Windows Defender Windefend AMSI Detection (Event ID 1116)
Pivot detection · T1059 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. 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.