Windows WMI Persistence: Script Event Consumer File Writes (scrcons.exe)

Flags file writes performed by scrcons.exe, indicating potential WMI script event consumer persistence activity.

FreeReviewedSigma · High · v2
Product
windows
Category
file_event
Author
Thomas Patzke (SigmaHQ), DRL 1.1
Published
2018-03-07
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

This rule flags file write events involving the WMI script event consumer executable located at C:\WINDOWS\system32\wbem\scrcons.exe. Attackers can use WMI event consumers to achieve persistence by executing scripts in response to system or management events. Detection relies on Windows file event telemetry that records writes to this specific WMI component, as well as the executable path in the event data.

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: Script Event Consumer File Writes (scrcons.exe)
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.