Windows UAC Bypass via NTFS Reparse Point: wusa.exe DLL Hijacking Process Behavior

Alerts on high-integrity wusa.exe launched from Temp update.msu with a dism.exe parent showing DismHost activity.

FreeReviewedSigma · High · v1
Product
windows
Category
process_creation
Author
Christian Burkard (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2021-08-30
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 a process-creation sequence consistent with a UAC bypass technique that uses an NTFS reparse point and wusa.exe DLL hijacking. It matches wusa.exe executions with specific command-line patterns and high/system integrity context, as well as a parent dism.exe invocation indicative of package/handler staging. Telemetry required is Windows process creation with full command lines and process integrity level data.

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 via NTFS Reparse Point: wusa.exe DLL Hijacking Process Behavior
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.