T1620: Reflective Code Loading
T1620 (Reflective Code Loading) is classified under the Defense Evasion tactic within the MITRE ATT&CK framework. Tradecraft designed to avoid detection, analysis, and eradication throughout their operational lifecycle, including process injection, file obfuscation, and disabling defensive telemetry. In telemetry gathered across enterprise endpoints and the EMBER 2018 benchmark, this technique was weaponized across 15 distinct malware families, totaling over 711 validated samples.
Technical Anatomy & Adversary Tradecraft
Adversaries leverage Reflective Code Loading to accomplish operational objectives while minimizing anomalous forensic footprints. When executing Reflective Code Loading, malicious binaries commonly interact directly with low-level Windows APIs, kernel mode drivers, or native scripting interfaces to bypass traditional file-integrity monitors and static antivirus signatures.
In modern multi-stage campaigns, T1620 is frequently observed functioning as an intermediate bridge: initial access payloads (such as spearphishing loaders or exploit macros) execute Reflective Code Loading to establish in-memory execution or persistence before staging secondary ransomware or data-exfiltration implants.
https://attack.mitre.org/techniques/T1620/.
Detection Engineering & Threat Hunting
Detecting Reflective Code Loading requires telemetry correlation across endpoint detection and response (EDR) agents, Sysmon event streams, and security information event management (SIEM) pipelines:
- Process Creation & Lineage: Monitor parent-child process anomalies where unexpected parent binaries (e.g., Office executables, web browsers, or script hosts) spawn command shells or native Windows utilities.
- API Hooking & Behavioral Telemetry: EDR platforms should flag rapid calls to memory allocation, process injection, or registry manipulation APIs originating from unbacked executable memory regions.
- Network Anomaly Correlation: Cross-reference endpoint execution timestamps with external network socket establishment to identify anomalous beaconing or covert data staging.
SOC Containment & Hardening Guidance
To mitigate risks associated with T1620 (Reflective Code Loading) across production infrastructure, security teams should implement the following defensive controls:
- Attack Surface Reduction (ASR): Enforce strict application control policies (WDAC or AppLocker) to restrict execution to signed and verified corporate binaries.
- Least Privilege & Credential Hygiene: Restrict local administrative privileges to prevent adversaries from tampering with defensive agents or escalating privileges.
- Network Microsegmentation: Restrict lateral communication across endpoint VLANs to prevent wormable payloads from utilizing Reflective Code Loading across adjacent network segments.
Cataloged Malware Families Utilizing T1620 (15 Families)
The following malware families in the SystemHelpDesk catalog have been verified utilizing T1620 (Reflective Code Loading):
| Family | Category | Sample Count | Technical Summary |
|---|---|---|---|
| noobyprotect | Packer | 136 | Noobyprotect (cataloged in threat telemetry under signatures including SoftwareBundler:Win32/Noobyprotect, Trojan.MalPack.NP, and PUA:Win32/NoobyProtect) is a c... |
| confuser | Packer | 120 | Confuser (and its prominent open-source successor, ConfuserEx, cataloged by security vendors as HackTool:MSIL/Confuser, VirTool:MSIL/Obfuscator, and Trojan:MSIL... |
| dynamer | Trojan | 110 | Dynamer (cataloged across security telemetry as Trojan:Win32/Dynamer, Trojan:Win32/Dynamer!ac, Trojan:Win32/Dynamer!rfn, and Trojan.Win32.Dynamer) is a prevalen... |
| vmprotbad | Trojan | 87 | VMProtBad (cataloged across security vendors under detections including Trojan:Win32/VMProtBad, Trojan:Win32/VMProtect, and Win32/VMProtBad) is a heuristic thre... |
| meterpreter | Hacktool | 78 | Meterpreter (cataloged across security vendors and threat intelligence databases under detections including HackTool:Win32/Meterpreter, Trojan:Win32/Meterpreter... |
| obsidium | Packer | 57 | Obsidium (cataloged across security vendors and binary analysis platforms under signatures including Packer:Win32/Obsidium, Trojan:Win32/Obsidium, and Trojan-Ra... |
| enigmaprotector | Packer | 50 | EnigmaProtector (cataloged across security vendors and threat intelligence databases under detections including Packer:Win32/EnigmaProtector, Trojan:Win32/Enigm... |
| cryptinject | Ransomware | 15 | Cryptinject (classified in antimalware definitions under designations including Ransom:Win32/Cryptinject, Trojan:Win32/Cryptinject, and VirTool:Win32/Cryptinjec... |
| enigma | Ransomware | 14 | Enigma (classified as Ransom:Win32/Enigma and Trojan-Ransom.Win32.Enigma) is an advanced Windows crypto-ransomware family designed for rapid and devastating cor... |
| vmpbad | Ransomware | 14 | Vmpbad (classified across antimalware research as Trojan:Win32/Vmpbad and Ransom:Win32/Vmpbad) is a heavily packed and armored trojan loader and crypto-ransomwa... |
| dimnie | Infostealer | 13 | Dimnie (first discovered in 2014 and thoroughly analyzed by security firms including Palo Alto Networks Unit 42) is an evasive modular infostealer and intellige... |
| pespin | Ransomware | 8 | Trojan:Win32/Pespin (or generic **Pespin Packer** heuristics) refers to detections associated with the 'PESpin' executable packer and protector. Originally desi... |
| morphine | Ransomware | 7 | Packer:Win32/Morphine is a highly notorious heuristic detection for a specific type of **Polymorphic Packer** and crypter. Morphine is not malware itself; it is... |
| donut | Ransomware | 1 | <h3>Executive Summary</h3> Donut is a highly sophisticated, open-source offensive security framework designed to generate position-independent shellcode from .N... |
| drooptroop | Trojan | 1 | <h3>Executive Summary</h3> Drooptroop is a highly specialized Dropper and Loader tool, frequently associated with Advanced Persistent Threat (APT) groups. Unlik... |