agentleFS
kaandgnshkaandgnsh/Claude-Blue/skills/dfir/memory-forensics/SKILL.md

memory-forensics

Skill0 starsChanged 13 days agoMITView on GitHub

Analyze Windows and Linux memory images with Volatility 3 to find malicious processes, injected code, network connections, command lines, persistence and credential-theft artefacts. Use when a memory dump (.raw, .lime, .vmem, hiberfil, crash dump) is available or when fileless malware or process injection is suspected.

  • Installs packages

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

Memory Forensics (Volatility 3)

Setup

pip install volatility3          # or clone https://github.com/volatilityfoundation/volatility3
vol -f mem.raw windows.info      # confirms symbols/profile load; Linux needs matching ISF symbols

Linux images need an ISF symbol file for the exact kernel (dwarf2json from vmlinux with debug symbols).

Triage sequence (Windows)

StepPluginLook for
Processeswindows.pslist, windows.psscan, windows.pstreeHidden processes (in psscan not pslist), wrong parents (e.g. lsass.exe not child of wininit.exe; svchost.exe not child of services.exe), misspelled names, odd paths
Command lineswindows.cmdlineEncoded PowerShell, LOLBins, paths in %TEMP%/AppData
Networkwindows.netscanConnections from processes that shouldn't talk (e.g. notepad.exe), listeners on unusual ports
Injectionwindows.malfindPAGE_EXECUTE_READWRITE private regions with MZ header or shellcode
Moduleswindows.dlllist, windows.ldrmodulesDLLs from user-writable paths; unlinked modules (InLoad/InInit/InMem = False)
Serviceswindows.svcscanServices with binaries in unusual paths or recently added
Handles/mutexwindows.handles --pid NKnown malware mutexes, handles to lsass.exe
Registrywindows.registry.hivelist, windows.registry.printkey --key "Software\Microsoft\Windows\CurrentVersion\Run"Persistence
Fileswindows.filescan, windows.dumpfiles --virtaddr 0x...Recover binaries/scripts for analysis
Process dumpwindows.pslist --pid N --dump, windows.memmap --pid N --dumpFeed to YARA/static analysis

YARA over memory: vol -f mem.raw windows.vadyarascan --yara-file rules.yar (plugin name/options vary by version — check vol -h).

Linux

linux.pslist, linux.pstree, linux.bash (shell history from memory), linux.lsof, linux.sockstat, linux.malfind, linux.check_modules / linux.lsmod (hidden kernel modules), linux.elfs.

Interpretation

  • Baseline parent/child relationships: SANS "Hunt Evil" poster is a practical reference.
  • Malfind has false positives (JIT engines: .NET, browsers, Java). Confirm with a dump + YARA/disassembly.
  • Correlate memory findings with disk timeline and EDR telemetry; record PID, process create time and virtual addresses.

Output template

Image: <file> sha256 <>  OS: <build>  Captured: <UTC>
Suspicious processes: <pid> <name> <ppid> <path> <reason>
Injection: <pid> <vad addr> <protection> <evidence>
Network: <pid> <local> → <remote> <state>
Persistence: <>
Extracted artefacts: <file> sha256 <>
Confidence & next steps: <>

Safety

Analyse on an isolated analysis workstation. Dumped executables are live malware — store in password-protected archives (infected) and never execute outside a sandbox.

Related skills

forensic-imaging, windows-artifacts, yara-authoring, credential-theft-detection, pe-static-analysis

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.