Windows Process Creation: WSReset.exe Used with Non-CONHOST Child Process

Alerts when wsreset.exe spawns a process other than conhost.exe, a potential UAC-bypass precursor.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
E.M. Anhaus (originally from Atomic Blue Detections, Tony Lambert), oscd.community, Florian Roth (SigmaHQ), DRL 1.1
Published
2019-10-24
Updated
2026-07-30

ATT&CK techniques

Priv Esc → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule flags process creation events where the parent process is wsreset.exe and the child process is not conhost.exe. Using wsreset.exe as a parent can indicate an attempt to trigger execution paths that lead to elevated actions, which matters because it may enable privilege escalation. It relies on Windows process creation telemetry, specifically the parent executable path and the spawned child executable identity (including OriginalFileName and conhost filtering).

Related detections9 linkedT1548.002 — drag to rearrange
Malicious FodHelper UAC Bypass via ms-settings Shell Command Hijack (via registry_set)
Suspicious Banana RAT UAC Skip Environment Variable in PowerShell
Malicious UAC Bypass via sdclt Handler Hijack (via registry_set)
Malicious UAC Bypass via ms-settings Handler Hijack (via registry_set)
Malicious DBatLoader DLL Sideloading via easinvoker.exe Loading netutils.dll (via image_load)
Suspicious dllhost.exe Spawned with CLSID and Anomalous Parent (via process_creation)
Malicious ms-settings DelegateExecute UAC Bypass Registry Change
Malicious User Account Control Bypass via Auto-Elevating Binary Hijack (via process_creation)
Suspicious Mock Trusted Directory with Trailing Space (via process_creation)
Windows Process Creation: WSReset.exe Used with Non-CONHOST Child Process
Pivot detection · T1548.002 · 9 related

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