Windows: WinRM Service Process Spawning Command-Line and Scripting Utilities

Flags suspicious child shells and admin utilities spawned by the WinRM host process (wsmprovhost.exe) on Windows.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Andreas Hunkeler (@Karneades), Markus Neis (SigmaHQ), DRL 1.1
Published
2021-05-20
Updated
2026-07-30

ATT&CK techniques

Initial Access
  1. Recon

  2. Resource Dev

  3. Execution

  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 identifies process creation events where the parent process is wsmprovhost.exe and the child process command image ends with common command-line, shell, scripting, and utility executables (such as cmd.exe, PowerShell variants, bash/sh, wsl, schtasks, certutil, whoami, and bitsadmin). Attackers can leverage WinRM to execute commands remotely, often via intermediate shell or administrative utilities to establish execution, persistence, or privilege escalation. The detection relies on Windows process creation telemetry including parent and image paths.

Related detections9 linkedT1190 — drag to rearrange
Malicious Node.js Process Spawning Unix Shell or Network Client
Malicious SharePoint ToolShell Exploitation via ToolPane Endpoint
Malicious Exchange Mailbox Export to ASPX via New-MailboxExportRequest
Suspicious Shell Spawned by ActiveMQ Java Process
Cleo Autorun Exploitation via Healthcheck File Drop
Suspicious SharePoint Worker Process Spawning Command Interpreter via ToolShell
Malicious IIS Worker Process Spawning Command Shell Reconnaissance
Potential StyleSmuggler (CVE-2026-75650) Exploitation Attempt - Magento GraphQL Styles Parameter (via webserver)
Cisco IOS XE Configuration Change by Web UI WSMA User
Windows: WinRM Service Process Spawning Command-Line and Scripting Utilities
Pivot detection · T1190 · 9 related

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