Windows Registry UAC Bypass Attempt via Windows Media Player osk.exe AppCompatFlags

Identifies registry AppCompatFlags entries for Windows Media Player osk.exe that may indicate a UAC bypass attempt.

FreeReviewedSigma · High · v1
Product
windows
Category
registry_set
Author
Christian Burkard (Nextron Systems) (SigmaHQ), DRL 1.1
Published
2021-08-23
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 writes that set the AppCompatFlags Compatibility Assistant store entry for Windows Media Player’s osk.exe path with a value of “Binary Data”. Attackers abuse these compatibility settings to influence how Windows launches executables and potentially bypass User Account Control protections. The detection relies on Windows registry set telemetry capturing the TargetObject path ending in the specified osk.exe Store location and the corresponding 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 UAC Bypass Attempt via Windows Media Player osk.exe AppCompatFlags
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.