Windows WMI Event Consumer with Encoded Payload Containing Suspicious Strings

Detects WMI event consumer encoded payloads containing suspicious execution-related strings on Windows.

FreeReviewedSigma · High · v1
Product
windows
Category
wmi_event
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2021-09-01
Updated
2026-07-30

ATT&CK techniques

Execution → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Defense Evasion

  5. Cred Access

  6. Discovery

  7. Lateral Movement

  8. Collection

  9. C2

  10. Exfiltration

  11. Impact

What it detects

This rule flags Windows WMI Event Consumer activity where an encoded value includes specific strings associated with suspicious memory/process execution behaviors. Such payloads can be used to hide commands or stage follow-on actions through WMI-driven execution. The detection relies on telemetry from WMI event data, specifically the presence of these substrings within the encoded field.

Related detections9 linkedT1047 — drag to rearrange
Malicious Impacket wmiexec Command Execution via WmiPrvSE Spawning cmd with Admin-Share Output Redirect (via process_creation)
Malicious QDoor Remote Proxy Execution via WMIC Node Process Call Create of svhost from Temp (via process_creation)
Malicious Remote Payload Deployment via WMIC Node Process Call Create with bitsadmin Transfer (via process_creation)
Malicious WMIexec Style Command Output Redirection to Local Admin Share
Suspicious Impacket Style Command Execution with ADMIN Share Output Redirect
Malicious Shadow Copy Deletion via WMIC via Process Creation (via process_creation)
Suspicious System Reconnaissance Output Redirected to PDF File (via process_creation)
Suspicious Phantom Taurus mssq.bat SQL Execution via WMI (via process_creation)
Malicious Antivirus Removal via WMIC Product Uninstall
Windows WMI Event Consumer with Encoded Payload Containing Suspicious Strings
Pivot detection · T1047 · 9 related

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