MITRE ATT&CK Technique
T1620Reflective Code Loading
- First Reported
- May 25, 2021
- Latest Reported
- Nov 17, 2026
Official 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](https://attack.mitre.org/techniques/T1129)).
Reflectively loaded payloads may be compiled binaries, anonymous files (only present in RAM), or just snubs of fileless executable code (ex: position-independent shellcode).(Citation: Introducing Donut)(Citation: S1 Custom Shellcode Tool)(Citation: Stuart ELF Memory)(Citation: 00sec Droppers)(Citation: Mandiant BYOL) For example, the `Assembly.Load()` method executed by [PowerShell](https://attack.mitre.org/techniques/T1059/001) may be abused to load raw code into the running process.(Citation: Microsoft AssemblyLoad)
Reflective code injection is very similar to [Process Injection](https://attack.mitre.org/techniques/T1055) except that the “injection” loads code into the processes’ own memory instead of that of a separate process. Reflective loading may evade process-based detections since the execution of the arbitrary code may be masked within a legitimate or otherwise benign process. Reflectively loading payloads directly into memory may also avoid creating files or other artifacts on disk, while also enabling malware to keep these payloads encrypted (or otherwise obfuscated) until execution.(Citation: Stuart ELF Memory)(Citation: 00sec Droppers)(Citation: Intezer ACBackdoor)(Citation: S1 Old Rat New Tricks)
Reflectively loaded payloads may be compiled binaries, anonymous files (only present in RAM), or just snubs of fileless executable code (ex: position-independent shellcode).(Citation: Introducing Donut)(Citation: S1 Custom Shellcode Tool)(Citation: Stuart ELF Memory)(Citation: 00sec Droppers)(Citation: Mandiant BYOL) For example, the `Assembly.Load()` method executed by [PowerShell](https://attack.mitre.org/techniques/T1059/001) may be abused to load raw code into the running process.(Citation: Microsoft AssemblyLoad)
Reflective code injection is very similar to [Process Injection](https://attack.mitre.org/techniques/T1055) except that the “injection” loads code into the processes’ own memory instead of that of a separate process. Reflective loading may evade process-based detections since the execution of the arbitrary code may be masked within a legitimate or otherwise benign process. Reflectively loading payloads directly into memory may also avoid creating files or other artifacts on disk, while also enabling malware to keep these payloads encrypted (or otherwise obfuscated) until execution.(Citation: Stuart ELF Memory)(Citation: 00sec Droppers)(Citation: Intezer ACBackdoor)(Citation: S1 Old Rat New Tricks)
- Tactics
- Stealth
- Platforms
- Linux, macOS, Windows
- MITRE Version
- 2.0
- Last Modified
- May 12, 2026
Reported Context (158)
- The proxy plug-ins reflectively load compiled Go programs into the current process's address space. Operation ShadowCloud’s GraphDoor Backdoor Uses SharePoint and Ably for C2
- After decrypting the final payload PE, BubbleLoader performs reflective loading. BubbleLoader Uses Patched Software and PNGs to Deliver Malware
- The article says Assembly.Load executed managed payloads without a normal on-disk assembly load. FBI Details Gootloader SEO Poisoning and WordPress Compromises
- The implant receives machine code from C2, allocates executable memory, and runs the payload without writing it to disk. Researchers Detail GhostFrame ESXi Implant Linked to Settra Activity
- The implant used a reflective loader to map an embedded x64 DLL into memory. Huntress Details AhsayCBS Intrusion With Hidden Webshells, XMRig Miner and C2 Implant
CVE (39)
Malware (306)
People (66)
Threat Actors (118)
MITRE ATT&CK (304)
Vendors (105)
Products (449)
Tools (252)
Industries (84)
Countries (91)
Note: Related entities, including threat actors, malware, CVEs, MITRE ATT&CK techniques, vendors, products, tools, countries, and industries, are shown when they appear in the same reporting. Their presence does not necessarily mean they were targeted, compromised, vulnerable, responsible for the activity, or directly involved in the incident.
