Suspicious PowerShell/WScript Activity in WMI Event Consumer Commands

Identifies WMI event consumer commands containing PowerShell/WScript download-and-execute patterns like Net.WebClient and IEX.

FreeReviewedSigma · High · v1
Product
windows
Category
wmi_event
Author
Florian Roth (Nextron Systems), Jonhnathan Ribeiro (SigmaHQ), DRL 1.1
Published
2019-04-15
Updated
2026-07-30

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 WMI event consumer command lines that reference scripting and download execution patterns, including PowerShell-style use of New-Object with Net.WebClient and DownloadString/DownloadFile, as well as common IEX/encoding and base64-related constructs. Such activity is relevant because WMI event subscriptions can be abused to run attacker-supplied scripts persistently or at scheduled triggers. It relies on telemetry from Windows WMI event logs that record the consumer Destination command text.

Related detections9 linkedT1059.005 — drag to rearrange
Suspicious Script Host Execution of Decoy-Named JavaScript Dropper (PS1Bot)
Malicious PathWiper Loader Script Execution from Windows Temp via WScript
Suspicious Office Application Spawning Script Or Shell Interpreter
Malicious Script Host Spawning PowerShell With Invoke-Expression (via process_creation)
Suspicious MSHTA VBScript WScript Shell Execution
Malicious Kimsuky VBE Payload Download via Curl to AppData and Execution (via process_creation)
Suspicious winrm.vbs LOLBAS Script Execution for Code Proxying
Malicious LitterDrifter VBScript Execution via wscript trash.dll
Suspicious Script Host Spawning PowerShell via BlindEagle Chain
Suspicious PowerShell/WScript Activity in WMI Event Consumer Commands
Pivot detection · T1059.005 · 9 related

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