Detect Image File Execution Options Injection in Microsoft Sentinel
Adversaries may establish persistence and/or elevate privileges by executing malicious content triggered by Image File Execution Options (IFEO) debugger values. IFEO enables developers to attach debuggers to applications. Registry keys in HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\{binary}.exe can be set with a Debugger value that allows a debugger to be launched automatically when the specified binary is executed. Adversaries abuse this by setting the Debugger value to their malicious payload — whenever the target binary executes, Windows launches the adversary's payload instead (with the target binary name as an argument). This can be used to replace legitimate processes, persist on reboot, or escalate privileges.
MITRE ATT&CK
- Tactic
- Privilege Escalation Persistence
- Technique
- T1546 Event Triggered Execution
- Sub-technique
- T1546.012 Image File Execution Options Injection
- Canonical reference
- https://attack.mitre.org/techniques/T1546/012/
KQL Detection Query
DeviceRegistryEvents
| where Timestamp > ago(24h)
| where RegistryKey has "Image File Execution Options"
| where RegistryValueName in~ ("Debugger", "GlobalFlag", "MitigationOptions")
| where ActionType in ("RegistryValueSet", "RegistryKeyCreated")
| extend TargetBinary = extract(@"Image File Execution Options\\([^\\]+)", 1, RegistryKey)
| extend DebuggerPayload = RegistryValueData
| extend IsHighValueTarget = TargetBinary in~ (
"sethc.exe", "utilman.exe", "osk.exe", "Magnify.exe", "Narrator.exe",
"DisplaySwitch.exe", "AtBroker.exe", "taskmgr.exe", "regedit.exe",
"msconfig.exe", "mmc.exe", "cmd.exe", "powershell.exe"
)
| extend SuspiciousDebugger = DebuggerPayload has_any (
"cmd.exe", "powershell", "mshta", "wscript", "cscript",
"rundll32", "regsvr32", "AppData", "Temp", "ProgramData"
)
| extend IsSilentExit = RegistryValueName =~ "GlobalFlag" and RegistryValueData == "512"
| project Timestamp, DeviceName, AccountName, ActionType, RegistryKey,
TargetBinary, RegistryValueName, DebuggerPayload,
IsHighValueTarget, SuspiciousDebugger, IsSilentExit,
InitiatingProcessFileName, InitiatingProcessCommandLine
| sort by Timestamp descDetects IFEO Debugger injection by monitoring the Image File Execution Options registry key for Debugger value additions. Classifies targets as high-value (accessibility binaries, system management tools) or general targets. Flags Debugger values pointing to suspicious executables (LOLBins, scripting engines, user-writable paths). Also detects GlobalFlag=512 modifications used for SilentProcessExit monitoring — an alternative IFEO-based persistence mechanism where a payload is registered to execute when a monitored process exits.
Data Sources
Required Tables
False Positives & Tuning
- Developers legitimately attaching debuggers (Visual Studio, WinDbg) to specific applications during development and testing — these should set Debugger to a known debugger path like vsjitdebugger.exe
- Just-In-Time (JIT) debugging configured by Visual Studio or Windbg installation which sets a global IFEO Debugger entry for all processes
- Application error reporting tools that register themselves as debuggers to capture crash dumps
- Security products that use IFEO to inject their monitoring DLLs or intercept specific process launches
Other platforms for T1546.012
Testing Methodology
Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.
- Test 1IFEO Debugger Injection on cmd.exe
Expected signal: Sysmon Event ID 13: TargetObject=Image File Execution Options\cmd.exe\Debugger, Details=C:\Windows\System32\notepad.exe. Process creation for reg.exe. If cmd.exe is then launched, notepad.exe starts with cmd.exe as its argument.
- Test 2IFEO GlobalFlag for SilentProcessExit
Expected signal: Sysmon Event ID 13 records: GlobalFlag set to 512 in IFEO\notepad.exe, and MonitorProcess set in SilentProcessExit\notepad.exe. The combination of GlobalFlag=512 and MonitorProcess registration is the SilentProcessExit technique.
- Test 3Enumerate All IFEO Debugger Registrations
Expected signal: Process creation for reg.exe with query /s flags. Read-only enumeration. Output reveals all IFEO Debugger and GlobalFlag values across all registered binaries.
References (5)
- https://attack.mitre.org/techniques/T1546/012/
- https://github.com/redcanaryco/atomic-red-team/blob/master/atomics/T1546.012/T1546.012.md
- https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/enabling-postmortem-debugging
- https://blogs.msdn.microsoft.com/mithuns/2009/08/14/image-file-execution-options-ifeo/
- https://www.deepinstinct.com/blog/lolbas-part-3
Unlock Pro Content
Get the full detection package for T1546.012 including response playbook, investigation guide, and atomic red team tests.