Windows ConHost Spawning Suspicious Script and Command-Line Child Processes

Flags conhost.exe spawning command/scripting utilities like PowerShell, MSHTA, or regsvr32.exe.

FreeReviewedSigma · High · v2
Product
windows
Category
process_creation
Author
Swachchhanda Shrawan Poudel (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2025-02-05
Updated
2026-07-31

ATT&CK techniques

Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule flags process creation events where conhost.exe spawns specific child executables associated with command execution and scripting, including cmd.exe, cscript.exe, mshta.exe, PowerShell variants, regsvr32.exe, and wscript.exe. This matters because conhost.exe is a trusted Windows component that can be used to launch script or utility interpreters as part of stealthy execution chains. The detection relies on process creation telemetry containing parent and child process image paths and, in some cases, original file names to match the invoked binaries.

Related detections9 linkedT1202 — drag to rearrange
Suspicious Child Process Creation from BgInfo.EXE on Windows
Windows: Suspicious Child Process Spawned by VsCode code.exe
Windows WSL Process Spawning Uncommon Child Executables
Windows: Alert on Unusual Child Process of Setres.EXE Spawning 'choice' Executables
Windows Process Creation: Detect Sysinternals Tool Name Impersonation by Executable
Windows ZipExec-Style Suspicious PowerShell/Command Execution with Password-Protected ZIP
Windows: Cmdl32.EXE Arbitrary File Download Indicator via /vpn and /lan Flags
Windows Process Creation: WSL (wsl.exe) Used for Arbitrary Command Execution
Windows renamed dctask64.exe execution via known IMPHASH values
Windows ConHost Spawning Suspicious Script and Command-Line Child Processes
Pivot detection · T1202 · 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.