Windows UAC bypass using wsreset.exe with high/SYSTEM integrity

Alerts when wsreset.exe is executed with elevated integrity (High or SYSTEM), indicating a potential UAC bypass attempt.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Christian Burkard (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2021-08-23
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 wsreset.exe runs with elevated integrity levels commonly associated with UAC bypass scenarios. Attackers abuse Windows components like wsreset.exe to attempt privilege escalation by launching a trusted binary in a context that indicates elevated execution. The detection relies on Windows process creation telemetry and the process integrity level reported for wsreset.exe (including High and SYSTEM-related SIDs).

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 UAC bypass using wsreset.exe with high/SYSTEM integrity
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.