Process Environment Block
Also called PEB.
User-mode struct holding a process's image path, modules, and parameters.
What it is
A user-mode data structure, reachable from a process's memory, that records its image path, command line, environment variables, and the linked lists of loaded modules the loader maintains. It is the user-space counterpart to the kernel's process record.
Why it matters
The PEB yields the command line and full image path that started a process, and its module lists can be compared against other views to reveal unlinked or hidden DLLs. Attackers sometimes tamper with PEB fields to spoof the apparent command line or image path.
In practice
Reading the PEB to recover the full command line of a living-off-the-land script that the process list showed only as a generic interpreter name.
What to look for
- Image path and command line that differ from the kernel's view.
- Loaded module lists that are missing modules seen in the VAD tree.
- Being debugged flags or odd heap settings.
Common mistake
Trusting it as ground truth. It lives in user memory, and malware can rewrite it to look legitimate.
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.
Read next
- EPROCESS: The kernel structure describing a running Windows process.
- Thread Environment Block: Per-thread struct holding stack bounds and thread-local state.
- Reflective DLL Loading: Loading a DLL from memory while bypassing the OS loader and its lists.