Reflective Code Loading

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).¹²³⁴⁵ For example, the `Assembly.Load()` method executed by PowerShell may be abused to load raw code into the running process.⁶ Reflective code injection is very similar to Process Injection 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.⁷⁸⁹¹⁰

1. Introducing Donut
2. S1 Custom Shellcode Tool
3. Stuart ELF Memory
4. 00sec Droppers
5. Mandiant BYOL
6. Microsoft AssemblyLoad
7. Stuart ELF Memory
8. 00sec Droppers
9. Intezer ACBackdoor
10. S1 Old Rat New Tricks

使用该技术的组织

断言

尚无指向该技术的公开断言。

记录自动入库·未人工复核；置信度与有效期按引用读取。