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
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 (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.