MEMORY FORENSICS & VOLATILITY 3: KERNEL OBJECTS, POOL SCANNING & CODE INJECTION

Architect deep volatile memory analysis competencies for B.Tech Computer Science & IT: Volatile RAM capture mechanics across hardware and hypervisor layers (WinPmem, LiME, AVML); the modernized Python 3 symbol-table architecture of Volatility 3; Windows executive kernel object traversal (EPROCESS, ActiveProcessLinks, Token structures); Direct Kernel Object Manipulation (DKOM) detection via heuristic pool tag scanning (psscan vs. pslist); memory-injected code detection (malfind, VAD descriptors, RWX memory permissions); socket recovery and network artifact carving (netscan); and automated volatility triage scripting in Python.

🧠 The Volatile Frontier: Ephemeral States, Kernel Structures & Fileless Intrusions

In modern advanced adversary tradecraft, sophisticated threat actors increasingly operate entirely within volatile physical memory (RAM). By executing fileless malware, reflective DLL injections, process hollowing, and in-memory credential harvesting (e.g. LSASS access), adversaries bypass traditional disk-based antivirus scanners, leave zero footprint on file system Master File Tables (MFT), and evade dead-box forensic imaging. Memory Forensics is the technical discipline of acquiring and analyzing a snapshot of physical volatile memory (DRAM) taken while the machine was powered on. Using the modernized Volatility 3 framework, incident responders reconstruct active running processes, trace unlinked execution blocks hidden by kernel rootkits via Direct Kernel Object Manipulation (DKOM), extract cleartext encryption keys (BitLocker, TLS session pre-masters), dissect Virtual Address Descriptors (VAD), and carve injected shellcode straight out of unbacked executable memory pages.

1. Volatile Memory Architecture: Physical RAM to Virtual Address Spaces
Architectural schematic illustrating how physical memory (DRAM) is acquired into raw image files and translated by Volatility 3 through Directory Table Bases (CR3 register) and symbol tables into per-process virtual memory spaces.
Physical Memory Mapping & Volatility 3 Symbol Engine Pipeline
MEMORY FORENSICS TRANSLATION & ANALYSIS PIPELINE:

[PHYSICAL HARDWARE: RAM CHIPS (DRAM) - e.g. 16 GB Physical Address Space]
                        β”‚
                        β–Ό (Live Acquisition via Kernel Driver: WinPmem / LiME / AVML)
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ RAW MEMORY DUMP FILE (memory.raw / memory.dmp / crash.dmp)                                    β”‚
β”‚ β€’ Unstructured sequential byte stream of physical pages (0x00000000 to 0x3FFFFFFFF).          β”‚
β”‚ β€’ Contains user applications, kernel executive pool, page tables, hardware buffers.           β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                        β”‚
                        β–Ό (Volatility 3 Architecture Translation)
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ VOLATILITY 3 TRANSLATION & SYMBOL RESOLUTION ENGINE                                           β”‚
β”‚ β€’ Replaces legacy Volatility 2 static profiles with dynamic JSON Symbol Tables (Intermediate  β”‚
β”‚   Symbol Format - ISF), auto-downloaded from Microsoft Symbol Server (PDBs) or Linux DWARF.   β”‚
β”‚ β€’ Locates the Kernel Directory Table Base (CR3 register): Resolves Virtual to Physical addrs. β”‚
β”‚ β€’ Multi-Layer Paging Walk: PML4 (Level 4) ──► PDPT (Level 3) ──► PD (Level 2) ──► PT (Page)   β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
                        β”‚
                        β–Ό (Parsed Operating System Abstraction)
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ RECONSTRUCTED EXECUTIVE KERNEL & USER SPACE OBJECTS:                                          β”‚
β”‚                                                                                               β”‚
β”‚ 1. Kernel Executive Pool : EPROCESS linked lists, ETHREADs, Drivers, Registry Hives.          β”‚
β”‚ 2. Virtual Address Descr : VAD Trees (Tracking memory permissions: PAGE_EXECUTE_READWRITE).   β”‚
β”‚ 3. Network Sockets       : TCP Endpoints, UDP Listeners, open handle tables.                  β”‚
β”‚ 4. Process Memory Spaces : Injected shellcode, unmapped PE binaries, LSASS credential tokens. β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
Architectural Paradigm Shift: Volatility 2 required manual profile selection (e.g. '--profile=Win10x64_19041'). Volatility 3 eliminates profiles entirely: it inspects the raw dump, identifies the kernel GUID/PDB signature, and uses precise Intermediate Symbol Format (ISF) JSON tables to map exact struct member offsets automatically.
Real-Time Example 1: Physical Memory Acquisition: Tools & Hardware Write Integrity
Analysis of physical RAM acquisition techniques. Contrasts software kernel drivers (WinPmem, LiME, Microsoft AVML) with hypervisor memory state suspension (VMware .vmem, VirtualBox .sav), examining memory smearing and driver footprint minimization.
RAM Acquisition Commands & Hypervisor Memory Extraction
PHYSICAL MEMORY ACQUISITION METHODOLOGY:

1. WINDOWS LIVE MEMORY CAPTURE VIA WINPMEM CLI:
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ β€’ Must be executed from an external USB drive to minimize overwriting unallocated memory!     β”‚
β”‚ β€’ Loads signed kernel driver (winpmem.sys) providing direct physical address read handles.    β”‚
β”‚                                                                                               β”‚
β”‚ Command Execution:                                                                            β”‚
β”‚ D:\Tools\winpmem.exe -volume_mode 2 -o E:\Evidence\case_01\mem_dump.raw                       β”‚
β”‚                                                                                               β”‚
β”‚ Modes:                                                                                        β”‚
β”‚   Mode 1: Uses \\Device\\PhysicalMemory (Blocked on modern Windows versions).                 β”‚
β”‚   Mode 2: Maps physical pages directly via PTE manipulation (Standard for 64-bit systems).    β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

2. LINUX LIVE MEMORY CAPTURE VIA LiME (LINUX MEMORY EXTRACTOR):
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ β€’ Loadable Kernel Module (LKM) compiled for the exact target kernel version:                  β”‚
β”‚   $ sudo insmod lime-6.8.0-generic.ko "path=/mnt/usb/linux_mem.lime format=raw"               β”‚
β”‚ β€’ Or using Microsoft AVML (Acquire Volatile Memory for Linux - Static User-Space Binary):     β”‚
β”‚   $ sudo ./avml /mnt/usb/linux_mem.lime                                                       β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

3. VIRTUALIZED & CLOUD INFRASTRUCTURE MEMORY CAPTURE (ZERO GUEST CONTAMINATION):
β€’ VMware ESXi / Workstation : Pause / Suspend VM ──► Carve the '.vmem' file from datastore.
β€’ Microsoft Hyper-V         : Create Checkpoint ──► Extract the saved runtime state (.bin / .vsv).
β€’ Cloud Instances (AWS EC2) : Execute EC2 Snapshot or instantiate AWS Elastic Disaster Recovery.

THE REALITY OF MEMORY SMEARING:
Because the host OS is executing concurrently while WinPmem copies gigabytes of RAM across the PCI
bus, pages at the beginning of the dump represent time T=0, while pages at the end represent T+60s.
Memory forensics algorithms are designed to handle atomic structure coherence despite smearing.
Acquisition Rule: Never install software on a suspect system to acquire RAM! Running installers or compiling kernel modules on the victim machine overwrites hundreds of megabytes of resident memory, destroying the very evidence you seek to recover. Always execute standalone portable acquisition binaries from an external write-blocked USB drive.
Real-Time Example 2: Windows Executive Kernel Structures: Dissecting EPROCESS & ActiveProcessLinks
Analysis of the Windows kernel process tracking architecture. Details the _EPROCESS structure, circular doubly-linked lists (ActiveProcessLinks), the Process Environment Block (PEB), access tokens, and Virtual Address Descriptors (VAD).
Windows Kernel _EPROCESS Linked List & Memory Structure Geometry
THE WINDOWS EXECUTIVE _EPROCESS STRUCTURAL ANATOMY:

Each process on Windows is represented in kernel space by a struct _EPROCESS object:
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ struct _EPROCESS (Kernel Executive Process Block)                                             β”‚
β”‚                                                                                               β”‚
β”‚ Offset (x64)   Field Name            Type / Description                                       β”‚
β”‚ ────────────   ──────────            ──────────────────                                       β”‚
β”‚ +0x2e8         UniqueProcessId       HANDLE (Process ID - PID)                                β”‚
β”‚ +0x2f0         ActiveProcessLinks    _LIST_ENTRY (Doubly-linked circular list pointers)       β”‚
β”‚                β”œβ”€β”€ Flink             Points to NEXT process's ActiveProcessLinks              β”‚
β”‚                └── Blink             Points to PREVIOUS process's ActiveProcessLinks          β”‚
β”‚ +0x3a0         Token                 _EX_FAST_REF (Security Access Token: SIDs, Privileges)   β”‚
β”‚ +0x3f0         ImageFileName         UCHAR[15] (Process name string, e.g. "svchost.exe")      β”‚
β”‚ +0x448         DirectoryTableBase    ULONG_PTR (CR3 register value: Page Directory Base)      β”‚
β”‚ +0x7c8         VadRoot               _RTL_AVL_TREE (Balanced tree of allocated memory ranges) β”‚
β”‚ +0x550         Peb                   _PEB (User-Mode Process Environment Block)               β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

HOW THE OPERATING SYSTEM ENUMERATES PROCESSES (pslist mechanism):
The kernel maintains a global list head: PsActiveProcessHead.
The OS traverses the doubly-linked chain using Flink:
  [PsActiveProcessHead] ──► [System (PID 4)] ──► [smss.exe] ──► [csrss.exe] ──► [explorer.exe] ──┐
          β–²                                                                                       β”‚
          β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
Architectural Concept: The Flink and Blink pointers in ActiveProcessLinks are what standard tools (Task Manager, Process Explorer, pslist) traverse. If an attacker unlinks a malicious node from this chain (DKOM), standard API queries completely miss the process, even while its threads remain active in the scheduler.
Real-Time Example 3: Uncovering Hidden Processes: Direct Kernel Object Manipulation (DKOM) vs. psscan
Contrasting linked-list traversal with heuristic pool tag scanning. Demonstrates how rootkits unlink ActiveProcessLinks to hide processes and shows how Volatility 3's windows.psscan scans physical RAM for Proc and Thread pool allocation tags.
DKOM Unlinking Attack vs. Heuristic Pool Tag Scanning (psscan)
THE DIRECT KERNEL OBJECT MANIPULATION (DKOM) ATTACK VS. PSSCAN TRIAGE:

1. THE DKOM UNLINKING MECHANISM (CWE-400 / MITRE ATT&CK T1014):
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ A kernel rootkit driver executes pointer reassignment directly in kernel RAM:                 β”‚
β”‚                                                                                               β”‚
β”‚ BEFORE ROOTKIT HOOK:                                                                          β”‚
β”‚   [explorer.exe] <═══════════> [MALWARE.EXE (PID 6644)] <═══════════> [notepad.exe]           β”‚
β”‚                                                                                               β”‚
β”‚ AFTER ROOTKIT UNLINKS MALWARE.EXE:                                                            β”‚
β”‚   [explorer.exe].Flink = &notepad.exe;                                                        β”‚
β”‚   [notepad.exe].Blink  = &explorer.exe;                                                       β”‚
β”‚                                                                                               β”‚
β”‚   RESULTING LIST:                                                                             β”‚
β”‚   [explorer.exe] <══════════════════════════════════════════════════> [notepad.exe]           β”‚
β”‚                                                                                               β”‚
β”‚   Isolated Node:                                                                              β”‚
β”‚   [MALWARE.EXE] (Still exists in physical memory! Threads still scheduled by CPU dispatcher!) β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

2. FORENSIC TRIAGE: windows.pslist VS. windows.psscan IN VOLATILITY 3:
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ A. windows.pslist:                                                                            β”‚
β”‚    β€’ Follows ActiveProcessLinks sequentially.                                                 β”‚
β”‚    β€’ Output: Shows explorer.exe and notepad.exe. MALWARE.EXE IS MISSING!                      β”‚
β”‚                                                                                               β”‚
β”‚ B. windows.psscan (POOL SCANNING HEURISTIC):                                                  β”‚
β”‚    β€’ Does NOT trust or follow ActiveProcessLinks!                                             β”‚
β”‚    β€’ Scans raw physical RAM byte-by-byte looking for executive pool allocation tags:          β”‚
β”‚      β”œβ”€β”€ 32-bit Pool Tag: 'Proc' (0x636F7250) or 'Pro\xe8'                                    β”‚
β”‚      └── 64-bit Pool Tag: 'Proc' / Kernel Object Type Indices                                 β”‚
β”‚    β€’ Output: Discovers MALWARE.EXE (PID 6644) intact in unallocated/active kernel pools!      β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
Forensic Comparison Command: $ python3 vol.py -f memory.raw windows.pslist > pslist.txt $ python3 vol.py -f memory.raw windows.psscan > psscan.txt $ diff pslist.txt psscan.txt Difference Finding: < (Not in pslist) > PID: 6644 ImageFileName: malware_beacon.exe ExitTime: N/A Offset: 0x1f4c0880 Any process visible in 'psscan' that is absent in 'pslist' with a null ExitTime is a confirmed DKOM rootkit artifact.
Real-Time Example 4: Injected Code Detection: VAD Trees, malfind & Memory Allocation Flags
Analysis of process memory injection detection. Explains the Virtual Address Descriptor (VAD) balanced binary tree, how the windows.malfind plugin identifies unbacked memory allocations with PAGE_EXECUTE_READWRITE permissions, and carves injected shellcode.
Virtual Address Descriptor (VAD) Tree & malfind Detection Criteria
VIRTUAL ADDRESS DESCRIPTOR (VAD) TREES & INJECTION MECHANICS:

WHAT IS THE VAD TREE?
The Windows kernel tracks every committed virtual memory range for a process using a self-balancing
AVL tree rooted at _EPROCESS.VadRoot. Each node (_MMVAD) defines:
  β€’ Starting & Ending Virtual Address (e.g. 0x00400000 - 0x00405000)
  β€’ Memory Protection Flags (PAGE_READONLY, PAGE_EXECUTE_READ, PAGE_EXECUTE_READWRITE)
  β€’ Memory Allocation Type (Private Memory vs. Mapped File / DLL image)

HOW VOLATILITY 3 malfind DETECTS INJECTIONS (PROCESS HOLLOWING / REFLECTIVE DLLs):
malfind traverses the VAD tree of every process searching for the "Holy Trinity" of injection:
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ MALFIND DETECTION RULE  β”‚ FORENSIC CRITERIA & ANOMALY SIGNATURE                               β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ 1. Protection Flag      β”‚ The VAD range is marked PAGE_EXECUTE_READWRITE (RWX: 0x40) or       β”‚
β”‚                         β”‚ PAGE_EXECUTE_READ (RX), permitting execution!                       β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ 2. Unbacked Memory      β”‚ The allocation is VadImageMap = False (Private Memory / MEM_PRIVATE)β”‚
β”‚                         β”‚ NOT backed by a legitimate file on disk (unlike normal DLLs)!       β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ 3. Executable Content   β”‚ The initial bytes in the page contain executable machine assembly   β”‚
β”‚                         β”‚ instructions or a carved PE header (MZ / 0x4D 0x5A)!                β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

SAMPLE VOLATILITY 3 malfind EXECUTION & OUTPUT:
$ python3 vol.py -f memory.raw windows.malfind.Malfind --pid 4120

PID    Process       Start Address    End Address      Protection               File Output
4120   svchost.exe   0x1f4c20000      0x1f4c21000      PAGE_EXECUTE_READWRITE   Disabled

Disassembly Preview:
0x1f4c2000:  dec    ebp
0x1f4c2001:  pop    edx
0x1f4c2002:  nop
0x1f4c2003:  call   0x1f4c2008       <-- Shellcode Delta-Offset Anchor!
0x1f4c2008:  pop    ebp              <-- Retrieves current instruction pointer into register!

Hex Dump:
4d 5a 90 00 03 00 00 00  04 00 00 00 ff ff 00 00  MZ..............
b8 00 00 00 00 00 00 00  40 00 00 00 00 00 00 00  ........@.......
Triage Insight: Legitimate Windows applications compiled with modern toolchains almost never allocate memory pages that are simultaneously Writable and Executable (violates W ^ X). An unbacked memory page marked PAGE_EXECUTE_READWRITE in a core service like svchost.exe or explorer.exe is an immediate high-confidence indicator of injected shellcode.
Real-Time Example 5: Network Artifact Carving: Socket Recovery via windows.netscan
Reconstructing network telemetry from volatile RAM. Explains how Volatility 3's windows.netscan plugin scans memory pools for TCP endpoints (_TCPT) and UDP listener structures to uncover terminated or active Command-and-Control (C2) connections.
Volatility 3 Network Telemetry Carving & Connection Mapping
VOLATILITY 3 NETWORK SOCKET ARTIFACT CARVING (windows.netscan):

WHY NETSCAN UNCOVERS TERMINATED CONNECTIONS:
Traditional netstat queries active OS tables. If malware connects to a C2 server, exfiltrates data,
and closes the socket, netstat immediately displays nothing.
However, in physical RAM, the underlying _TCP_ENDPOINT and _UDP_ENDPOINT structures remain
preserved in kernel pool memory until overwritten by new network allocations hours later!

VOLATILITY 3 NETSCAN COMMAND & TELEMETRY OUTPUT:
$ python3 vol.py -f memory.raw windows.netscan.NetScan

Offset          Proto  Local Address        Local Port  Foreign Address      Foreign Port  State        PID   Owner        Created
0x1f4c4890      TCPv4  192.168.100.50       49152       198.51.100.25        4444          ESTABLISHED  4120  svchost.exe  2026-11-04 14:10:02
0x1f4c8920      TCPv4  192.168.100.50       49188       203.0.113.88         80            CLOSED       6644  malware.exe  2026-11-04 14:05:12
0x1f4ce100      UDPv4  0.0.0.0              5355        *:*                  *             LISTENING    1040  svchost.exe  2026-11-04 12:00:00

CORRELATION ANALYSIS OF NETSCAN RESULTS:
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ FINDING 1: REVERSE SHELL ESTABLISHED FROM HOLLOWED PROCESS:                                   β”‚
β”‚ β€’ Local Socket   : 192.168.100.50:49152                                                       β”‚
β”‚ β€’ Foreign Address: 198.51.100.25:4444 (Attacker Metasploit Handler!)                          β”‚
β”‚ β€’ Owning Process : svchost.exe (PID 4120) ──► MATCHES THE MALFIND INJECTION DISCOVERED EARLIERβ”‚
β”‚ β€’ Forensic Reality: svchost.exe NEVER connects out to public port 4444 under normal conditionsβ”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ FINDING 2: HISTORICAL CLOSED C2 CHECK-IN:                                                     β”‚
β”‚ β€’ Socket State   : CLOSED                                                                     β”‚
β”‚ β€’ Foreign Address: 203.0.113.88:80 (C2 Staging Server)                                        β”‚
β”‚ β€’ Owning Process : malware.exe (PID 6644) ──► MATCHES THE UNLINKED DKOM ROOTKIT PROCESS!      β”‚
β”‚ β€’ Creation Time  : 14:05:12 UTC (Preceded the reverse shell by exactly 4 minutes, 50 seconds) β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
Correlation Power: By pairing 'windows.malfind' with 'windows.netscan', investigators connect the technical anomaly (injected shellcode in PID 4120) to real-world network infrastructure (outbound socket connection to 198.51.100.25:4444), establishing an unassailable evidentiary link.
Real-Time Example 6: Extracting Credential Secrets: LSASS Injection & LSA Secrets Dumps
Extracting credential material from volatile memory images. Demonstrates using Volatility 3 plugins to parse registry hives in RAM (windows.registry.hivelist), dumping local SAM database hashes (windows.hashdump), and carving cached domain LSA secrets.
In-Memory Registry Hive Resolution & SAM/LSA Credential Extraction
CREDENTIAL RECOVERY FROM VOLATILE RAM (OFFLINE TRIAGE):

ADVANTAGE OVER LIVE CREDENTIAL DUMPING:
Live tools (Mimikatz) must inject into lsass.exe on an active system, triggering EDR alerts and
potentially crashing the LSASS daemon.
Memory forensics extracts credentials OFFLINE from the static memory dump with zero EDR detection!

1. LOCATE REGISTRY HIVES IN RAM:
$ python3 vol.py -f memory.raw windows.registry.hivelist.HiveList

Offset          File Path
0x84021000      \Device\HarddiskVolume2\Windows\System32\config\SYSTEM
0x84089000      \Device\HarddiskVolume2\Windows\System32\config\SAM

2. EXTRACT LOCAL NTLM PASSWORD HASHES (windows.hashdump):
Requires pointing to virtual offsets of SYSTEM and SAM hives:
$ python3 vol.py -f memory.raw windows.hashdump.Hashdump

User                   RID   LMHash                            NTHash
Administrator          500   aad3b435b51404eeaad3b435b51404ee  3b4e3e533604c5a9f0d8c5708c5ae48b
Guest                  501   aad3b435b51404eeaad3b435b51404ee  31d6cfe0d16ae931b73c59d7e0c089c0
secops_aarav           1001  aad3b435b51404eeaad3b435b51404ee  8846f7eaee8fb117ad06bdd830b7586c

3. EXTRACT CACHED DOMAIN CREDENTIALS & LSA SECRETS:
$ python3 vol.py -f memory.raw windows.cachedump.Cachedump
$ python3 vol.py -f memory.raw windows.lsadump.Lsadump

[+] DefaultPassword: EnterprisePassword#2026
[+] DPAPI Master Keys Extracted from LSASS memory space!
Remediation Insight: If memory analysis uncovers cleartext passwords or NTLM hashes for domain accounts, incident responders immediately mandate enterprise-wide Kerberos krbtgt account resets and force password rotations across compromised user accounts.
Real-Time Example 7: Automated Volatility 3 Memory Triage Pipeline in Python
Building an automated memory forensic triage pipeline in Python. Uses subprocess orchestration to run core Volatility 3 plugins (psscan, malfind, netscan), parses output tables, correlates anomalous indicators, and produces an incident triage report.
Python (Automated Volatility 3 Incident Triage Script: vol3_triage.py)
import subprocess
import json
import sys
from typing import List, Dict

class VolatilityAutomatedTriager:
    """
    Automates end-to-end memory forensics triage using Volatility 3:
      1. Runs pslist and psscan to identify unlinked DKOM rootkit processes.
      2. Runs malfind to locate injected executable memory regions.
      3. Runs netscan to discover active and terminated C2 connections.
      4. Correlates findings into a unified triage report.
    """
    def __init__(self, memory_image_path: str, vol3_cli_path: str = "vol"):
        self.image = memory_image_path
        self.vol = vol3_cli_path

    def run_plugin(self, plugin_name: str) -> str:
        """Executes Volatility 3 plugin with JSON/text output."""
        cmd = [self.vol, "-f", self.image, plugin_name]
        print(f"[*] Executing Volatility 3 plugin: {plugin_name}...")
        try:
            res = subprocess.check_output(cmd, text=True, stderr=subprocess.DEVNULL)
            return res
        except subprocess.CalledProcessError as e:
            return ""

    def triage_memory_sample(self) -> dict:
        triage_report = {
            "image": self.image,
            "dkom_hidden_pids": [],
            "injected_processes": [],
            "suspicious_network_conns": []
        }

        # Step 1: Detect DKOM by comparing pslist and psscan
        pslist_raw = self.run_plugin("windows.pslist.PsList")
        psscan_raw = self.run_plugin("windows.psscan.PsScan")

        pslist_pids = set()
        for line in pslist_raw.splitlines():
            parts = line.split()
            if len(parts) > 2 and parts[0].isdigit():
                pslist_pids.add(parts[0]) # PID

        for line in psscan_raw.splitlines():
            parts = line.split()
            if len(parts) > 2 and parts[0].isdigit():
                pid = parts[0]
                # If process in psscan but NOT in pslist βž” DKOM Rootkit!
                if pid not in pslist_pids:
                    triage_report["dkom_hidden_pids"].append({
                        "pid": pid,
                        "process_name": parts[1] if len(parts) > 1 else "Unknown"
                    })

        # Step 2: Detect Code Injections via malfind
        malfind_raw = self.run_plugin("windows.malfind.Malfind")
        for line in malfind_raw.splitlines():
            if "PAGE_EXECUTE_READWRITE" in line:
                parts = line.split()
                if len(parts) >= 2:
                    triage_report["injected_processes"].append({
                        "pid": parts[0],
                        "process": parts[1],
                        "protection": "PAGE_EXECUTE_READWRITE"
                    })

        # Step 3: Parse Network Sockets via netscan
        netscan_raw = self.run_plugin("windows.netscan.NetScan")
        for line in netscan_raw.splitlines():
            if "ESTABLISHED" in line:
                parts = line.split()
                if len(parts) >= 7:
                    triage_report["suspicious_network_conns"].append({
                        "proto": parts[1],
                        "local": f"{parts[2]}:{parts[3]}",
                        "foreign": f"{parts[4]}:{parts[5]}",
                        "pid": parts[7]
                    })

        return triage_report

if __name__ == "__main__":
    print("==========================================================================")
    print("      VOLATILITY 3 AUTOMATED FORENSIC TRIAGE PIPELINE")
    print("==========================================================================")
    
    # Mock output simulation for academic curriculum demonstration
    simulated_summary = {
        "image": "windows10_compromised.raw",
        "dkom_hidden_pids": [{"pid": "6644", "process_name": "malware_beacon.exe"}],
        "injected_processes": [{"pid": "4120", "process": "svchost.exe", "protection": "PAGE_EXECUTE_READWRITE"}],
        "suspicious_network_conns": [{"proto": "TCPv4", "local": "192.168.100.50:49152", "foreign": "198.51.100.25:4444", "pid": "4120"}]
    }

    print(f"[*] Target Memory Dump: {simulated_summary['image']}")
    print(f"\n[!] HIGH-PRIORITY TRIAGE FINDINGS:")
    print(f"  β”œβ”€β”€ Confirmed DKOM Rootkit Processes : {len(simulated_summary['dkom_hidden_pids'])}")
    for d in simulated_summary["dkom_hidden_pids"]:
        print(f"  β”‚   └── Hidden PID {d['pid']}: {d['process_name']} (Unlinked from ActiveProcessLinks)")
    print(f"  β”œβ”€β”€ Injected Memory Allocations (RWX): {len(simulated_summary['injected_processes'])}")
    for i in simulated_summary["injected_processes"]:
        print(f"  β”‚   └── Injected PID {i['pid']}: {i['process']} (VAD RWX Memory Carved)")
    print(f"  └── Active C2 Sockets Correlated     : {len(simulated_summary['suspicious_network_conns'])}")
    for c in simulated_summary["suspicious_network_conns"]:
        print(f"      └── PID {c['pid']} connected to Attacker C2: {c['foreign']}")
Triage Pipeline Output: ========================================================================== VOLATILITY 3 AUTOMATED FORENSIC TRIAGE PIPELINE ========================================================================== [*] Target Memory Dump: windows10_compromised.raw [!] HIGH-PRIORITY TRIAGE FINDINGS: β”œβ”€β”€ Confirmed DKOM Rootkit Processes : 1 β”‚ └── Hidden PID 6644: malware_beacon.exe (Unlinked from ActiveProcessLinks) β”œβ”€β”€ Injected Memory Allocations (RWX): 1 β”‚ └── Injected PID 4120: svchost.exe (VAD RWX Memory Carved) └── Active C2 Sockets Correlated : 1 └── PID 4120 connected to Attacker C2: 198.51.100.25:4444 Pipeline Value: The automated Python pipeline correlates process anomalies, kernel unlinking, and network sockets into a single threat narrative within minutes, allowing Tier-3 incident responders to focus directly on remediation.
Real-Time Example 8: Debugging Memory Forensics Pitfalls & Symbol Table Triage
Troubleshooting common memory analysis failures: resolving missing symbol table errors (Intermediate Symbol Format / ISF), handling compressed pagefile swapping artifacts, and diagnosing corrupted CR3 Directory Table Bases.
Volatility 3 Troubleshooting & Symbol Engine Configuration
MEMORY FORENSICS PITFALLS & VOLATILITY 3 CONFIGURATION TRIAGE:

// ==============================================================================
// PITFALL 1: MISSING SYMBOL TABLE / INTERMEDIATE SYMBOL FORMAT (ISF) FAILURE
// SYMPTOM: Volatility 3 throws an unhandled exception:
//   "volatility3.framework.exceptions.SymbolError: No suitable kernel symbol table found"
// CAUSE: Volatility 3 requires exact debugging symbols matching the Windows kernel build
// (ntkrnlmp.pdb) or Linux kernel DWARF data to know struct member offsets.
// If the analysis machine has no internet connection, it cannot download the PDB!
// REMEDIATION:
// 1. In offline air-gapped labs, manually pre-populate the symbols directory:
//    volatility3/symbols/windows/ntkrnlmp.pdb/...
// 2. Or run the Volatility symbol downloader utility on an internet-connected workstation:
//    python3 -m volatility3.framework.symbols.windows.pdbconv -p ntkrnlmp.pdb -o symbols.json
// ==============================================================================

// ==============================================================================
// PITFALL 2: CORRUPTED CR3 REGISTER / VIRTUAL MEMORY ADDRESS MAPPING
// SYMPTOM: All plugins (pslist, malfind) return 0 rows, yet the dump is 16 GB!
// CAUSE: The acquisition driver failed to locate the primary Kernel Directory Table Base
// (DTB / CR3), preventing virtual-to-physical address translation.
// REMEDIATION: Force DTB Scanning or Specify DTB Offset:
// Run the layer scan plugin to locate potential DTBs across physical memory:
//   python3 vol.py -f memory.raw windows.dtb.DTB
// Then pass the valid base explicitly:
//   python3 vol.py -f memory.raw --dtb 0x1aa000 windows.pslist.PsList
// ==============================================================================

// ==============================================================================
// PITFALL 3: THE SWAPPED-OUT MEMORY TRAP (PAGEFILE.SYS NEGLECT)
// SYMPTOM: An analyst dumps process memory, but critical strings/code return zeros.
// CAUSE: Windows paged out the inactive memory regions to C:\pagefile.sys or hiberfil.sys
// before physical memory was dumped!
// REMEDIATION: Incorporate Pagefile Layers:
// Acquire pagefile.sys alongside raw physical RAM and configure Volatility to map both:
//   python3 vol.py -f memory.raw --single-location file:///path/pagefile.sys windows.malfind
// ==============================================================================
Triage Summary: - Symbol Resolution Errors: Pre-cached Windows kernel PDB symbol tables into the local Volatility 3 cache directory. - Missing CR3 Directory Table Base: Recovered valid DTB addresses using the 'windows.dtb' layer scanner. - Paged-out Memory Voids: Ingested pagefile.sys alongside raw physical RAM dumps to reconstruct swapped-out virtual memory pages.
Real-Time Example 9: Memory Forensics & Volatility 3 Reference Matrix
A comprehensive reference summary pairing memory forensic domains, Volatility 3 plugins, kernel structures, investigative objectives, and academic exam keywords for B.Tech engineering students.
Memory Forensics & Volatility 3 Specification Reference Matrix
MEMORY FORENSICS & VOLATILITY 3 SPECIFICATION MATRIX:
β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚ INVESTIGATIVE DOMAIN    β”‚ VOLATILITY 3 PLUGIN SYNTAX   β”‚ TARGET STRUCTURE β”‚ CORE FORENSIC OUTCOME         β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ Process Listing         β”‚ windows.pslist.PsList        β”‚ ActiveProcess-   β”‚ Enumerates active processes;  β”‚
β”‚ (Standard Traversal)    β”‚                              β”‚ Links list head  β”‚ maps PID, PPID, start times   β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ Pool Tag Scanning       β”‚ windows.psscan.PsScan        β”‚ Executive Pool   β”‚ Uncovers unlinked DKOM        β”‚
β”‚ (Hidden Process Enum)   β”‚                              β”‚ 'Proc' pool tags β”‚ rootkits and terminated tasks β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ Process Tree Hierarchy  β”‚ windows.pstree.PsTree        β”‚ PPID to PID      β”‚ Visualizes parentage; reveals β”‚
β”‚                         β”‚                              β”‚ Relationships    β”‚ anomalous execution chains    β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ Injected Code Detection β”‚ windows.malfind.Malfind      β”‚ VAD Tree nodes   β”‚ Identifies unbacked RWX pages,β”‚
β”‚ (Process Hollowing)     β”‚ --pid <PID>                  β”‚ MEM_PRIVATE      β”‚ carves injected shellcode / PEβ”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ Network Sockets         β”‚ windows.netscan.NetScan      β”‚ _TCP_ENDPOINT &  β”‚ Reconstructs active & closed  β”‚
β”‚ (C2 Infrastructure)     β”‚                              β”‚ _UDP_ENDPOINT    β”‚ TCP/UDP C2 beacon connections β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ Local SAM Hashes        β”‚ windows.hashdump.Hashdump    β”‚ SYSTEM & SAM     β”‚ Extracts local NTLM password  β”‚
β”‚ (Credential Harvesting) β”‚                              β”‚ In-Memory Hives  β”‚ hashes without touching disk  β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ Command-Line Arguments  β”‚ windows.cmdline.CmdLine      β”‚ Process Environ- β”‚ Extracts cleartext CLI flags, β”‚
β”‚                         β”‚                              β”‚ ment Block (PEB) β”‚ script parameters, passwords  β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ Kernel Driver Listing   β”‚ windows.driverscan.DriverScanβ”‚ Driver Objects   β”‚ Detects unsigned malicious    β”‚
β”‚ (Rootkit Drivers)       β”‚                              β”‚ (_DRIVER_OBJECT) β”‚ kernel-mode rootkit drivers   β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚ TOP 5 MEMORY FORENSIC PRINCIPLES:                                                                         β”‚
β”‚ 1. Acquire RAM First: Follow RFC 3227; capture volatile memory before power state transitions.            β”‚
β”‚ 2. Compare pslist vs. psscan: Identify DKOM rootkit unlinking by contrasting list and pool results.       β”‚
β”‚ 3. Hunt for Unbacked RWX Pages: Focus malfind on PAGE_EXECUTE_READWRITE pages lacking disk backing.       β”‚
β”‚ 4. Correlate Sockets to PIDs: Link foreign C2 IP connections directly to injected process IDs.            β”‚
β”‚ 5. Verify Offline Symbols: Ensure Intermediate Symbol Format (ISF) tables match kernel builds.            β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
Academic & Professional Standard: Volatile memory forensics provides definitive evidence of advanced in-memory threat activity. Mastering kernel executive structures, VAD trees, pool tag scanning, and Volatility 3 automation equips B.Tech students to detect fileless malware, reverse engineer live rootkits, and extract ephemeral indicators of compromise during major cyber incident investigations.