Detect Image File Execution Options Injection in Elastic Security
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/
Elastic Detection Query
registry where event.type in ("change", "creation") and
registry.path : "*\\Image File Execution Options\\*" and
registry.value : ("Debugger", "GlobalFlag", "MitigationOptions") and
(
registry.data.strings : ("*cmd.exe*", "*powershell*", "*mshta*", "*wscript*", "*cscript*", "*rundll32*", "*regsvr32*", "*AppData*", "*\\Temp\\*", "*ProgramData*") or
process.name : ("sethc.exe", "utilman.exe", "osk.exe", "Magnify.exe", "Narrator.exe", "DisplaySwitch.exe", "AtBroker.exe") or
(registry.value : "GlobalFlag" and registry.data.strings : "512")
)Detects Image File Execution Options (IFEO) injection by monitoring registry modifications under the IFEO key for Debugger, GlobalFlag, or MitigationOptions values. Flags high-value accessibility binary targets and suspicious debugger payloads pointing to scripting engines or writable directories.
Data Sources
Required Tables
False Positives & Tuning
- Legitimate software developers attaching debuggers (e.g., Visual Studio, WinDbg) to applications under test — verify registry author and debugger path against known development workstations
- Application compatibility shims or crash dump tools (e.g., ProcDump, Dr. Watson) that legitimately set IFEO Debugger values for specific binaries
- Security software such as EDR agents or AV engines that set MitigationOptions or GlobalFlag on high-risk processes as a protective measure
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.