t1574-hijack-execution-flow

name	T1574_hijack-execution-flow
description	Adversaries may execute their own malicious payloads by hijacking the way operating systems run programs.
category	configuration
version	18.1
author	cyberstrike-official
tags	["mitre-attack","enterprise","t1574","persistence","privilege-escalation","defense-evasion","linux","macos","windows"]
technique_id	T1574
tactic	persistence
all_tactics	["persistence","privilege-escalation","defense-evasion"]
platforms	["Linux","macOS","Windows"]
mitre_url	https://attack.mitre.org/techniques/T1574
tech_stack	["linux","macos","windows"]
cwe_ids	["CWE-276"]
chains_with	["T1574.001","T1574.004","T1574.005","T1574.006","T1574.007","T1574.008","T1574.009","T1574.010","T1574.011","T1574.012","T1574.013","T1574.014"]
prerequisites	[]
severity_boost	{"T1574.001":"Chain with T1574.001 for deeper attack path","T1574.004":"Chain with T1574.004 for deeper attack path","T1574.005":"Chain with T1574.005 for deeper attack path"}

T1574 Hijack Execution Flow

High-Level 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.

Kill Chain Phase

• Persistence (TA0003)
• Privilege Escalation (TA0004)
• Defense Evasion (TA0005)

Platforms: Linux, macOS, Windows

What to Check

• Identify if Hijack Execution Flow technique is applicable to target environment
• Check Linux systems for indicators of Hijack Execution Flow
• Check macOS systems for indicators of Hijack Execution Flow
• Check Windows systems for indicators of Hijack Execution Flow
• Verify mitigations are bypassed or absent (10 known mitigations)
• Assess detection coverage (1 detection strategies)

How to Test

Manual Testing

1. Identify Attack Surface: Determine if the target environment is susceptible to Hijack Execution Flow by examining the target platforms (Linux, macOS, Windows).

2. Assess Existing Defenses: Review whether mitigations for T1574 are in place. If defenses are absent or misconfigured, this technique may be exploitable.

3. Execute Test: Use tools and methods described in the MITRE ATT&CK page and external references below.

Note: No Atomic Red Team tests available for this technique. See Atomic Red Team GitHub for updates.

Remediation Guide

M1052 User Account Control