Process Injection: Thread Local Storage
- ID
- T1055.005
- Tactics
- TA0004 Privilege Escalation, TA0005 Stealth
- Sub-technique of
- T1055 Process Injection
- Platforms
- Windows
- Data sources
- Module Load, Process Access, Process Modification, OS API Execution
- Source
- attack.mitre.org
- MITRE last modified
- 12 May 2026
Adversaries may inject malicious code into processes via thread local storage (TLS) callbacks in order to evade process-based defenses as well as possibly elevate privileges. TLS callback injection is a method of executing arbitrary code in the address space of a separate live process.
TLS callback injection involves manipulating pointers inside a portable executable (PE) to redirect a process to malicious code before reaching the code's legitimate entry point. TLS callbacks are normally used by the OS to setup and/or cleanup data used by threads. Manipulating TLS callbacks may be performed by allocating and writing to specific offsets within a process’ memory space using other Process Injection techniques such as Process Hollowing.[1]
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 TLS callback injection may also evade detection from security products since the execution is masked under a legitimate process.
Detection
- DET0467 Detection Strategy for TLS Callback Injection via PE Memory Modification and Hollowing
Data components: Module Load, Process Access, Process Modification, OS API Execution
Mitigations (1)
- M1040 Behavior Prevention on Endpoint
Some endpoint security solutions can be configured to block some types of process injection based on common sequences of behavior that occur during the injection process.
