CyberKit

EPROCESS

Also called Executive Process Block.

The kernel structure describing a running Windows process.

What it is

The executive process block is the kernel's master record for a process, holding its PID, name, parent reference, token, handle table, VAD tree root, and the links that thread it into the active-process list. Memory tools locate and parse these structures to enumerate processes.

Why it matters

Because every process has an EPROCESS, finding them directly in memory recovers processes that have been hidden from the OS or terminated, and their fields (parent PID, create time, exit time) anchor a process timeline that user-mode tooling cannot fake.

In practice

Comparing the doubly linked active-process list against EPROCESS blocks found by scanning, and flagging one that was unlinked to hide a running implant.

What to look for

  • Processes in the scan view but missing from the active list.
  • Creation and exit times that do not fit the timeline.
  • Parent process IDs that point to an unexpected parent.

Common mistake

Relying on one view of the process list. A rootkit can unlink an EPROCESS from the list that tools walk.

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.

Read next

Sources