Skip to content
AS
03 / Digital Forensics2026

Memory Forensics Triage

Volatility 3 plus twelve heuristics for process hollowing, injection, credential dumping and rootkits — output as a report a lawyer could read.

Volatility 3DFIRPythonHTML reports
Case file
Role
Solo build — research, engineering, documentation, release
Status
v1.0.0 · 8/8 tests
Year
2026
Position
03 of 13
Case 03 / memory-forensics-triageArchitecture · Evidence · Signal

01 — Context

The problem worth solving.

Attackers live in memory. Manual Volatility runs are slow, inconsistent between analysts, and the output is unreadable to anyone outside the incident room.

02 — Approach

How it was built.

  1. 01

    Drive Volatility 3 plugins through a single triage pipeline.

  2. 02

    Score twelve behavioural heuristics per process instead of dumping every table.

  3. 03

    Correlate injection chains, hidden processes and VAD anomalies into candidate findings.

  4. 04

    Render HTML and JSON reports for both technical and non-technical readers.

03 — Architecture

The shape of the system.

01Input

Memory image plus profile and optional IOC list.

02Collection

Volatility 3 plugins gather processes, modules, handles and network state.

03Heuristics

Twelve rules flag hollowing, injection, dumping and rootkit behaviour.

04Correlation

Findings link across processes into an attack narrative.

05Report

HTML for humans, JSON for tooling, severity per finding.

04 — Evidence

Receipts, not adjectives.

12heuristics
8/8tests passing
HTML + JSONreport formats

05 — Hiring signal

“Kernel-level understanding rather than script-kiddie tooling: hidden processes, VAD anomalies and injection chains, explained in plain language.”

Ships working systemsDocuments the methodExplains the trade-offsKeeps evidence attached

06 — What's next

Still being built.

Add timeline correlation across memory and disk artefacts, then a Windows/Linux parity pass.