CyberKit

Process Hollowing

Malware starts a legit process, then swaps its guts for malicious code.

What it is

A code-injection technique where an attacker launches a legitimate process in a suspended state, unmaps its original image, and replaces it with malicious code before resuming it. The process keeps a trusted name and path.

Why it matters

It lets malware masquerade as a benign, often signed program, evading naive process-name checks. Detecting it usually means comparing the on-disk image to what is actually mapped in memory.

In practice

A process listed as "svchost.exe" whose in-memory code does not match the real binary on disk: a classic hollowing tell.

What to look for

  • A trusted process whose memory image does not match its file on disk.
  • A legitimate binary started suspended by an unusual parent.
  • Executable private memory inside a process that should only have mapped images.

Common mistake

Trusting the process name and path. Hollowing keeps both; the memory contents are what changed.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

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

Read next

  • Memory Acquisition: Capturing a live system's RAM into an image for analysis.
  • Rootkit: Stealth malware that hides itself deep in the OS.
  • Living off the Land: Attackers abuse built-in, trusted tools instead of dropping malware.

Sources