huntrule

Windows WMI Event Consumer (scrcons.exe) Creates Named Pipe

Flags scrcons.exe creating a Windows named pipe, using named pipe creation event telemetry.

FreeReviewedSigma · Medium · v2
Product
windows
Category
pipe_created
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2021-09-01
Updated
2026-07-31
AnalysisDetection

ATT&CK techniques

Execution

  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. C2

  13. Exfiltration

  14. Impact

What it detects

This rule matches when the WMI Event Consumer process scrcons.exe is observed creating a named pipe. Attackers may leverage WMI event consumers to execute or stage activity via inter-process communication, so named pipe creation tied to this binary can be a useful indicator. The detection relies on Windows telemetry that records named pipe creation events and includes the creating process image path.

Reporting behind it

Related detections9 linkedT1047 — drag to rearrange
Lateral Movement via WMIC Remote Process Creation
Malicious UAT-8302 Remote Process Execution via wmic
Malicious Remote Encryptor Execution via WMIC Process Call Create (Chaos Ransomware)
Malicious Impacket Wmiexec Remote Command Execution Pattern
Malicious Shadow Copy Deletion Via WMI
Suspicious Remote Process Creation via WMIC Process Call Create (via process_creation)
Suspicious System Reconnaissance via WMI Command-Line Queries (via process_creation)
Malicious Impacket WMIexec Process Execution (via process_creation)
Suspicious Child Process Spawned by WMI Provider Host (via process_creation)
Windows WMI Event Consumer (scrcons.exe) Creates Named Pipe
Pivot detection · T1047 · 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.