MITRE ATT&CK Technique
T1574Hijack Execution Flow
- First Reported
- —
- Latest Reported
- —
Official Description
Adversaries may execute their own malicious payloads by hijacking the way operating systems run programs. Hijacking execution flow can be for the purposes of persistence, since this hijacked execution may reoccur over time. Adversaries may also use these mechanisms to elevate privileges or evade defenses, such as application control or other restrictions on execution.
There are many ways an adversary may hijack the flow of execution, including by manipulating how the operating system locates programs to be executed. How the operating system locates libraries to be used by a program can also be intercepted. Locations where the operating system looks for programs/resources, such as file directories and in the case of Windows the Registry, could also be poisoned to include malicious payloads.
There are many ways an adversary may hijack the flow of execution, including by manipulating how the operating system locates programs to be executed. How the operating system locates libraries to be used by a program can also be intercepted. Locations where the operating system looks for programs/resources, such as file directories and in the case of Windows the Registry, could also be poisoned to include malicious payloads.
- Tactics
- Stealth, Execution
- Platforms
- Linux, macOS, Windows
- MITRE Version
- 2.0
- Last Modified
- May 12, 2026
Sub-techniques (12)
T1574.001 · DLLT1574.004 · Dylib HijackingT1574.005 · Executable Installer File Permissions WeaknessT1574.006 · Dynamic Linker HijackingT1574.007 · Path Interception by PATH Environment VariableT1574.008 · Path Interception by Search Order HijackingT1574.009 · Path Interception by Unquoted PathT1574.010 · Services File Permissions WeaknessT1574.011 · Services Registry Permissions WeaknessT1574.012 · COR_PROFILER