Operator On The Wire
Join
← Back to Knowledge Base
BLUE TEAM / THREAT HUNT / WINDOWS / PERSISTENCE

IFEO Abuse

This note documents detection patterns related to IFEO Abuse within Windows environments.


Direct Indicators

LogEvent IDMeaningForensic ValueNotes
Sysmon12Registry object create/deleteCriticalDetects creation of IFEO keys.
Sysmon13Registry value setCriticalCore indicator for Debugger, GlobalFlag, VerifierDlls.
Security4657Registry value modifiedHighNative audit if enabled.
Sysmon1Process creationCriticalShows hijacked binary launching attacker payload.
Security4688Process creationCriticalParent-child context after trigger.
Sysmon11File createMediumPayload written before IFEO registration.

Indirect Indicators

IndicatorWhat To Look ForForensic ValueNotes
Debugger value addedExecutable redirectedCriticalCore abuse primitive.
Accessibility binary targetedsethc.exe, utilman.exe, osk.exeCriticalClassic persistence.
Trusted binary launches unusual childHijacked process starts payloadCriticalStrong execution clue.
IFEO key on workstationRare outside dev/debug environmentsHighStrong anomaly.
SilentProcessExit pair existsAdvanced persistence chainHighOften paired with IFEO abuse.
GlobalFlag unusualLoader manipulationHighAdvanced technique clue.

Common Tools

ToolUsage
reg.exeDirect registry modification
PowerShellNew-ItemProperty / Set-ItemProperty
regedit.exeManual registry abuse
custom malwareIFEO persistence

Relevant Artifacts

  • Sysmon Event IDs 12, 13, 1, 11
  • Security Event IDs 4657, 4688
  • Registry path:
    • HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\
  • Common values:
    • Debugger
    • GlobalFlag
    • VerifierDlls
  • Prefetch:
    • REG.EXE
    • POWERSHELL.EXE
  • Amcache / ShimCache
  • EDR registry timeline

MITRE ATT&CK References

  • T1546.012 Image File Execution Options Injection
  • T1112 Modify Registry

Decision Tree

  1. Which executable targeted?

    • Accessibility binary
    • User app
    • System utility
  2. Which value set?

    • Debugger
    • GlobalFlag
    • VerifierDlls
  3. Trigger observed?

    • Process launch
    • Login screen abuse
    • User execution
  4. Follow-up activity?

    • SYSTEM shell
    • Persistence
    • Credential access
  5. Expand:

    • SilentProcessExit
    • Adjacent registry persistence
    • Payload location
  6. Scope:

    • Single IFEO key
    • Multiple binaries
    • Campaign pattern

Example Detection Templates

KQL

Sysmon
| where EventID in (12,13)
| where TargetObject has "Image File Execution Options"
| project TimeGenerated, Computer, User, TargetObject, Details
SecurityEvent
| where EventID == 4688
| where ParentProcessName has_any ("sethc.exe","utilman.exe","osk.exe")
| project TimeGenerated, Computer, ParentProcessName, NewProcessName

EQL

registry where registry.path like "*Image File Execution Options*"
sequence by host.name with maxspan=10m
  [ registry where registry.path like "*Image File Execution Options*" ]
  [ process where process.parent.name in ("sethc.exe","utilman.exe","osk.exe") ]

Sigma

title: IFEO Abuse Detection
id: 1e8d5a33-ifeo-abuse
status: experimental
description: Detects Image File Execution Options registry abuse
references:
  - https://attack.mitre.org/
author: Vergil
date: 2026-03-07
logsource:
  product: windows
  service: sysmon
detection:
  selection:
    EventID:
      - 12
      - 13
  keywords:
    TargetObject|contains: 'Image File Execution Options'
  condition: selection and keywords
fields:
  - TargetObject
  - Details
falsepositives:
  - Debugging environments
level: high
tags:
  - attack.persistence
  - attack.t1546.012

Mitigation & Hardening

Control AreaMitigationEffectivenessNotes
Registry monitoringAlert on IFEO writesCriticalCore visibility
Baseline IFEO keysRare entries reviewedCriticalLow false positives
Protect accessibility binariesWatch trigger pathsHighCommon abuse path
Central registry telemetryPreserve changesHighStrong forensic value
Restrict admin rightsReduce registry abuseHighPrevent persistence