Process Injection
Running malicious code inside another live process to inherit its trust and hide.
What it is
A family of techniques that execute attacker code within the address space of a separate, usually legitimate, process. Living inside a trusted process lets the code borrow that process's identity, privileges, and network access.
Why it matters
It is one of the most common defense-evasion methods and defeats naive process-name allow-listing, since the malicious activity appears to come from a benign program. Detecting it means comparing a process's on-disk image to what is actually mapped in memory: the core of memory forensics.
In practice
Malware allocating memory in a running browser and starting a thread there, so its code and traffic look like the browser's.
What to look for
- Calls such as WriteProcessMemory or CreateRemoteThread across processes.
- Executable memory regions in a process that are not backed by a file on disk.
- Normal processes like notepad making network connections.
Common mistake
Trusting the process name. Injection runs malicious code inside a legitimate process on purpose.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Collection Plan
Build a host collection command list, ordered by volatility.
- Windows Host Case
An alert on a live Windows workstation: read the event logs and the Registry, rebuild the timeline, then decide what to collect.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Volatility 3 Open source
A widely used open source framework for analyzing memory images with plugins. Our notes.
-
Velociraptor Open source
Can collect memory and query live process memory across many hosts. Our notes.
-
CrowdStrike Falcon Commercial
EDR agents watch memory activity on the host, such as injection and unbacked code.
ATT&CK techniques
- T1055: Process Injection
Read next
- Process Hollowing: Malware starts a legit process, then swaps its guts for malicious code.
- DLL Injection: Forcing a target process to load an attacker-supplied library.
- Memory Acquisition: Capturing a live system's RAM into an image for analysis.