Adversaries may inject malicious code into suspended and hollowed processes in order to evade process-based defenses. Process hollowing is a method of executing arbitrary code in the address space of a separate live process. Process hollowing is commonly performed by creating a process in a suspended state then unmapping/hollowing its memory, which can then be replaced with malicious code. A victim process can be created with native Windows API calls such as <code>CreateProcess</code>, which includes a flag to suspend the processes primary thread. At this point the process can be unmapped using APIs calls such as <code>ZwUnmapViewOfSection</code> or <code>NtUnmapViewOfSection</code> before being written to, realigned to the injected code, and resumed via <code>VirtualAllocEx</code>, <code>WriteProcessMemory</code>, <code>SetThreadContext</code>, then <code>ResumeThread</code> respectively.12 This is very similar to Thread Local Storage but creates a new process rather than targeting an existing process. This behavior will likely not result in elevated privileges since the injected process was spawned from (and thus inherits the security context) of the injecting process. However, execution via process hollowing may also evade detection from security products since the execution is masked under a legitimate process.
- Leitch Hollowing
- Elastic Process Injection July 2017
Groups using this technique
| Group | Name | Country |
|---|---|---|
| grp_g1018 | TA2541 | — |
| grp_g1043 | BlackByte | — |
| grp_g0078 | Gorgon Group | — |
| grp_g0099 | APT-C-36 | — |
| grp_g0094 | Kimsuky | DPRK |
| grp_g0045 | menuPass | — |
| grp_g0040 | Patchwork | — |
| grp_g0027 | Threat Group-3390 | China |
Claims
No public claim points at this technique yet.
Auto-ingested and not human-reviewed; confidence and validity read by citation.