Windows remote PowerShell session activity via wsmprovhost.exe process relationships

Alerts when wsmprovhost.exe is seen as a process or parent process, indicating remote PowerShell via WinRM.

FreeReviewedSigma · Medium · v1
Product
windows
Category
process_creation
Author
Roberto Rodriguez @Cyb3rWard0g (SigmaHQ), DRL 1.1
Published
2019-09-12
Updated
2026-07-30

ATT&CK techniques

Execution → Lateral Movement
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Persistence

  5. Priv Esc

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule flags process creation where wsmprovhost.exe appears either as the executing image or as the parent process image. wsmprovhost.exe is the WinRM host component used to support remote PowerShell sessions, so its presence in the process chain indicates an active remote PowerShell execution context. It relies on Windows process creation telemetry, specifically the image and parent image paths ending with wsmprovhost.exe.

Related detections9 linkedT1059.001 — drag to rearrange
Windows Remote PowerShell via PS Classic (wsmprovhost.exe, HostName=ServerRemoteHost)
Windows Remote PowerShell Session via PS Module ContextInfo and wsmprovhost.exe
WinRM Remote Access to LSASS via wsmprovhost.exe (Windows Process Access)
Malicious Script Host Spawning PowerShell in Gootloader Chain
Suspicious PsExec Service Launching Encoded PowerShell Payload
Suspicious PowerShell Remote Script Execution via IEX DownloadString
Malicious SharePoint ToolShell Post-Exploitation via Encoded PowerShell (via process_creation)
Suspicious In-Memory PowerShell Execution from Web Server via Automation Assembly (via image_load)
Malicious Qilin Chrome Credential Harvesting Script Execution via IPScanner (via process_creation)
Windows remote PowerShell session activity via wsmprovhost.exe process relationships
Pivot detection · T1059.001 · 9 related

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