Windows UAC bypass using NTFS reparse point to place a hijack DLL in Temp

Alerts on file events pointing to a Temp legacy kernel32 DLL within user AppData, consistent with UAC bypass via reparse/DLL targeting.

FreeReviewedSigma · High · v2
Product
windows
Category
file_event
Author
Christian Burkard (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2021-08-30
Updated
2026-07-31

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 file events where an attacker attempts to drop a specific DLL into the per-user temporary AppData path, matching the NTFS reparse point UAC-bypass staging pattern. Such behavior can enable wusa.exe DLL hijacking to run attacker-controlled code with elevated privileges. It relies on file telemetry that records the target filename path, specifically under C:\Users\ and ending with the referenced DLL name in the Local\Temp directory.

Related detections9 linkedT1548.002 — drag to rearrange
Possible UAC Bypass via easinvoker Spawning Batch Script (via process_creation)
Suspicious UAC Bypass by Disabling Admin Consent Prompt via registry_set
Malicious Cloud Atlas UAC Bypass via fodhelper (via process_creation)
Suspicious computerdefaults.exe Spawning Child Process
Suspicious UAC Bypass via control.exe App Paths or Shell Open Command Hijack
Malicious UAC Bypass via COMAutoApprovalList Registry Modification (via registry_set)
Suspicious UAC Bypass via COMAutoApprovalList Registry Modification (via registry_set)
Malicious UAC Bypass via explorer.exe NOUACCHECK Argument
Suspicious UAC Bypass via ms-settings Shell Command Hijack (via registry_set)
Windows UAC bypass using NTFS reparse point to place a hijack DLL in Temp
Pivot detection · T1548.002 · 9 related

Changelog

v2
  1. v2
    Candidate ingested via manual entry.2026-07-31
  2. v1
    No changelog recorded for this version.2026-07-30

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