Operator On The Wire
Join
← Back to Knowledge Base
BLUE TEAM / THREAT HUNT / WINDOWS / PRIVILEGE ESCALATION

UAC Bypass

This note documents detection patterns related to UAC Bypass within Windows environments.


Direct Indicators

LogEvent IDMeaningForensic ValueNotes
Security4688Process creationCriticalDetects auto-elevated binary abuse and resulting payloads.
Sysmon1Process creationCriticalBest lineage source for bypass chains.
Sysmon13Registry value setCriticalCommon registry hijacks used by UAC bypass methods.
Sysmon12Registry object create/deleteHighRegistry preparation before trigger.
Security4672Special privileges assignedHighElevated token appears after bypass.
Sysmon11File createMediumPayload or helper file staging.

Indirect Indicators

IndicatorWhat To Look ForForensic ValueNotes
Auto-elevated binary launches shellfodhelper, computerdefaults, sdcltCriticalClassic bypass pattern.
HKCU hijack before triggerShell open command overrideCriticalCore registry primitive.
Elevated child without consent UISilent elevationCriticalStrong bypass clue.
Temp/AppData payload launched elevatedUser path elevated executionCriticalStrong anomaly.
Registry cleanup after launchKey removed quicklyHighSkilled operator behavior.
Short-lived auto-elevated processTrigger binary exits fastHighCommon bypass timing.

Common Tools

ToolUsage
fodhelper.exeRegistry hijack UAC bypass
computerdefaults.exeAuto-elevated trigger
sdclt.exeLegacy bypass
reg.exeRegistry setup
PowerShellRegistry automation

Relevant Artifacts

  • Security Event IDs 4688, 4672
  • Sysmon Event IDs 1, 12, 13, 11
  • Registry paths:
    • HKCU\Software\Classes\ms-settings\Shell\Open\command
  • Trigger binaries:
    • fodhelper.exe
    • computerdefaults.exe
    • sdclt.exe
  • Prefetch for trigger binary
  • Amcache / ShimCache

MITRE ATT&CK References

  • T1548.002 Bypass User Account Control

Decision Tree

  1. Which trigger binary?

    • fodhelper
    • computerdefaults
    • sdclt
  2. Registry modified?

    • HKCU hijack
    • Command override
  3. Elevated child appears?

    • cmd
    • powershell
    • payload
  4. Cleanup observed?

    • Registry delete
    • Temp file removal
  5. Expand:

    • Adjacent privesc
    • Persistence
    • Defender tampering
  6. Scope:

    • Single bypass
    • Repeated method
    • Toolkit chain

Example Detection Templates

KQL

Sysmon
| where EventID == 13
| where TargetObject has "ms-settings"
| project TimeGenerated, Computer, TargetObject, Details
SecurityEvent
| where EventID == 4688
| where ParentProcessName has_any ("fodhelper.exe","computerdefaults.exe","sdclt.exe")
| project TimeGenerated, Computer, ParentProcessName, NewProcessName

EQL

registry where registry.path like "*ms-settings*"
sequence by host.name with maxspan=5m
  [ registry where registry.path like "*ms-settings*" ]
  [ process where process.parent.name in ("fodhelper.exe","computerdefaults.exe","sdclt.exe") ]

Sigma

title: UAC Bypass Detection
id: 4f2c8a13-uac-bypass
status: experimental
description: Detects registry-based UAC bypass techniques
references:
  - https://attack.mitre.org/
author: Vergil
date: 2026-03-07
logsource:
  product: windows
  service: sysmon
detection:
  selection:
    EventID: 13
  keywords:
    TargetObject|contains: 'ms-settings'
  condition: selection and keywords
fields:
  - TargetObject
  - Details
falsepositives:
  - Rare legitimate software
level: high
tags:
  - attack.privilege_escalation
  - attack.t1548.002

Mitigation & Hardening

Control AreaMitigationEffectivenessNotes
Registry monitoringAlert on ms-settings hijackCriticalCore signal
Watch auto-elevated binariesHigh-value trigger setCriticalLow false positives
Preserve registry historyCatch cleanup attemptsHighStrong forensic value
UAC hardeningHighest notification levelHighReduces abuse
Restrict local admin rightsReduce trigger successHighPrevent escalation