Windows Registry: Detect DelegateExecute UAC bypass via TargetObject path

Alerts on registry set events targeting \open\command\DelegateExecute with empty Details, consistent with a UAC bypass attempt.

FreeReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
frack113 (SigmaHQ), DRL 1.1
Published
2022-01-05
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 registry set activity where the TargetObject ends with '\open\command\DelegateExecute' and the Details field is empty. Attackers can use DelegateExecute mechanisms to attempt privilege escalation by bypassing UAC using method chains that rely on registry-stored COM command execution. The detection relies on telemetry from Windows registry set events, matching the specific TargetObject path pattern and an empty Details value.

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 Registry: Detect DelegateExecute UAC bypass via TargetObject path
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.