Process Injection: Portable Executable Injection
- ID
- T1055.002
- Tactics
- TA0004 Privilege Escalation, TA0005 Stealth
- Sub-technique of
- T1055 Process Injection
- Platforms
- Windows
- Data sources
- Process Access, Process Modification, Process Creation, File Creation
- Source
- attack.mitre.org
- MITRE last modified
- 12 May 2026
Adversaries may inject portable executables (PE) into processes in order to evade process-based defenses as well as possibly elevate privileges. PE injection is a method of executing arbitrary code in the address space of a separate live process.
PE injection is commonly performed by copying code (perhaps without a file on disk) into the virtual address space of the target process before invoking it via a new thread. The write can be performed with native Windows API calls such as VirtualAllocEx and WriteProcessMemory, then invoked with CreateRemoteThread or additional code (ex: shellcode). The displacement of the injected code does introduce the additional requirement for functionality to remap memory references. [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 PE injection may also evade detection from security products since the execution is masked under a legitimate process.
Detection
- DET0106 Behavioral Detection of PE Injection via Remote Memory Mapping
Data components: Process Access, Process Modification, Process Creation, File Creation
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.
Groups (2)
Software (12)
- S0030 Carbanak
- S0260 InvisiMole
- S0330 Zeus Panda
- S0342 GreyEnergy
- S0681 Lizar
- S1063 Brute Ratel C4
- S1138 Gootloader
- S1145 Pikabot
- S1158 DUSTPAN
- S1229 Havoc
- S9024 SPAWNCHIMERA
- S9037 RustyWater
