Techniques › T1055.003 › AN0822
AN0822 Analytic 0822
Windows · attack.mitre.org · ATT&CK Enterprise v19.2
<p>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).</p>
- Detects
- T1055.003 Thread Execution Hijacking
- Part of
- DET0295 Behavioral Detection of Thread Execution Hijacking via Thread Suspension and Context Switching
Log sources and channels
Exactly as MITRE states them in x_mitre_log_source_references. Where a channel is vague, it is vague in the source; kevmap does not tidy it.
| Log source | Channel | Data component |
|---|---|---|
| WinEventLog:Sysmon | EventCode=10 | DC0035 Process Access |
| WinEventLog:Sysmon | EventCode=8 | DC0020 Process Modification |
| etw:Microsoft-Windows-Kernel-Process | API Calls | DC0021 OS API Execution |
| WinEventLog:Sysmon | EventCode=1 | DC0032 Process Creation |
Mutable elements
Parameters MITRE marks as environment-specific. These are the knobs you are expected to tune; they are why an analytic is not a rule.
| Field | Description |
|---|---|
TargetProcessList | Sensitive processes that should never be targeted for thread hijack attempts |
TimeWindow | Expected delay between SuspendThread and ResumeThread events; tight thresholds reduce evasion |
SuspiciousThreadContextRegions | Memory regions or offsets that should not be targeted for SetThreadContext |
ParentProcessAnomalyThreshold | Score deviation of the parent/child relationship in a thread injection chain |