T1620: Reflective Code Loading
Tactics: Stealth. Platforms: Linux, macOS, Windows.
Adversaries may reflectively load code into a process in order to conceal the execution of malicious payloads.
MITRE's description
Adversaries may reflectively load code into a process in order to conceal the execution of malicious payloads. Reflective loading involves allocating then executing payloads directly within the memory of the process, vice creating a thread or process backed by a file path on disk (e.g., Shared Modules). Reflectively loaded payloads may be compiled binaries, anonymous files (only present in RAM), or just snubs of fileless executable code (ex: position-independent shellcode).
Telemetry that detects it
- Module Load
- OS API Execution
- Process Access
- Process Creation
- Script Execution
D3FEND countermeasures
- D3-PSEP: Process Segment Execution Prevention (Harden)
- D3-SAOR: Segment Address Offset Randomization (Harden)
Procedure examples
- During the 3CX Supply Chain Attack, AppleJeus leverages the publicly available open-source project DAVESHELL to convert PE-COFF files to position-independent code to reflectively load the payload into memory.
- BADHATCH can copy a large byte array of 64-bit shellcode into process memory and execute it with a call to CreateThread.
- BRUSHFIRE has executed its commands within memory and is not saved on disk.
- Brute Ratel C4 has used reflective loading to execute malicious DLLs.
32 documented uses in all. These are a sample.
MITRE ATT&CK Enterprise 19.2. © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation.