Windows WMI Persistence via Security Event 4662 on WMI subscription namespace

Alerts on Security Event 4662 indicating access to WMI Namespace objects with "subscription" in the name.

FreeReviewedSigma · Medium · v2
Product
windows
Service
security
Author
Florian Roth (Nextron Systems), Gleb Sukhodolskiy, Timur Zinniatullin oscd.community (SigmaHQ), DRL 1.1
Published
2017-08-22
Updated
2026-07-31

ATT&CK techniques

Persistence → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

Identifies access events in the Windows Security log where an account interacts with the WMI namespace containing "subscription". This activity is commonly associated with setting up or modifying WMI event filters and their command-line event consumers, which attackers can use for persistence. The detection relies on Security log Event ID 4662 telemetry with ObjectType set to "WMI Namespace" and ObjectName containing "subscription".

Related detections9 linkedT1546.003 — drag to rearrange
Malicious WMI Registration - PowerShell (via powershell)
Malicious System Crash Behavior Manipulation - WMImplant - Registry (via registry_event)
Windows WMI Event Consumer with Encoded Payload Containing Suspicious Strings
PowerShell WMI Event Subscription Persistence via New-CimInstance
Windows Process Creation: WMIC.exe ActiveScriptEventConsumer Creation Attempt
Windows Security 4624 Logon for scrcons.exe Indicating Remote WMI ActiveScriptEventConsumers
WMI scrcons.exe Loading Script and WMI DLLs via Image Load (Windows)
Windows WMI Backdoor in Exchange Transport Agent via WMI Event Filter Execution
Windows WMI Event Subscription Creation (Sysmon Event 19/20/21)
Windows WMI Persistence via Security Event 4662 on WMI subscription namespace
Pivot detection · T1546.003 · 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.