Windows Registry UAC Bypass via Event Viewer Command Key (mscfile shell open command)

Alerts on registry changes to the mscfile shell open command key consistent with an Event Viewer UAC bypass technique.

FreeReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
Florian Roth (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2017-03-19
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 modifications to the Windows Event Viewer-related command key under the mscfile\shell\open\command path. Attackers may use this location to redirect how Event Viewer launches associated commands, enabling UAC bypass or privilege escalation. The detection relies on Windows registry set telemetry capturing TargetObject changes ending with '\mscfile\shell\open\command'.

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 UAC Bypass via Event Viewer Command Key (mscfile shell open command)
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.