Cross-source coverage

T1055.003 / ATT&CK

Process Injection: Thread Execution Hijacking

5 rules across 4 sources.

From MITRE ATT&CK 19.2

Adversaries may inject malicious code into hijacked processes in order to evade process-based defenses as well as possibly elevate privileges. Thread Execution Hijacking is a method of executing arbitrary code in the address space of a separate live process.

Thread Execution Hijacking is commonly performed by suspending an existing process then unmapping/hollowing its memory, which can then be replaced with malicious code or the path to a DLL. A handle to an existing victim process is first created with native Windows API calls such as OpenThread. At this point the process can be suspended then written to, realigned to the injected code, and resumed via SuspendThread , VirtualAllocEx, WriteProcessMemory, SetThreadContext, then ResumeThread respectively.

This is very similar to Process Hollowing but targets an existing process rather than creating a process in a suspended state.

Running code in the context of another process may allow access to the process's memory, system/network resources, and possibly elevated privileges. Execution via Thread Execution Hijacking may also evade detection from security products since the execution is masked under a legitimate process.

Platforms
Windows
Telemetry
WinEventLog:Sysmonetw:Microsoft-Windows-Kernel-Process

How MITRE says to detect it DET0295

Behavioral Detection of Thread Execution Hijacking via Thread Suspension and Context Switching

Windows Analytic 0822

Detects hijacking of an existing thread (OpenThread) through a behavioral chain involving thread suspension (SuspendThread), memory modification (VirtualAllocEx + WriteProcessMemory), context manipulation (SetThreadContext), and thread resumption—all within another live process's address space (ResumeThread).

  • WinEventLog:Sysmon EventCode=10
  • WinEventLog:Sysmon EventCode=8
  • etw:Microsoft-Windows-Kernel-Process API Calls
  • WinEventLog:Sysmon EventCode=1

SigmaHQ/sigma

2 rules
Detection Severity Format
HackTool - LittleCorporal Generated Maldoc Injection High Sigma
Remote Thread Creation In Uncommon Target Image Medium Sigma

Wazuh Core Ruleset

1 rule
Detection Severity Format
Possible code injection by on · win.eventdata.targetImage = (?i)(synchost\.exe|svchost\.exe) Low Wazuh XML

elastic/detection-rules

1 rule
Detection Severity Format
Potential Process Injection via PowerShell High Elastic TOML

splunk/security_content

1 rule
Detection Severity Format
PowerShell PInvoke Process Injection API Chain Undefined SPL

Detection rules belong to the projects that publish them and remain under their own licenses. This site indexes and links to them; it claims no rights in them.