Windows: Suspicious Child Process Spawned by scrcons.exe (Script Event Consumer)

Alerts on rare child processes spawned by scrcons.exe, which may indicate abuse of Script Event Consumer for execution.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Sittikorn S (SigmaHQ), DRL 1.1
Published
2021-06-21
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 process creation where the parent process is Script Event Consumer (scrcons.exe) and the child executable matches a set of common script execution and living-off-the-land binaries. Attackers may abuse scrcons.exe to launch additional processes for execution, scripting, or indirect payload delivery. Telemetry required is Windows process creation events containing parent and child image paths.

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: Suspicious Child Process Spawned by scrcons.exe (Script Event Consumer)
Pivot detection · T1047 · 9 related

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