conducting-memory-forensics-with-volatility

conducting-memory-forensics-with-volatility is a skill for Claude Code from oyi77/1ai-skills. It costs 88 tokens per session (1,088 once invoked), scanned A, original, MIT.

A guide to investigating a computer's RAM with Volatility 3, a tool for examining memory snapshots. It can reveal running processes, injected code, network connections, malware, credentials, and encryption keys.

In plain words
What is it for?
Use it during incident response to investigate process injection, fileless malware, credential theft, rootkits, and other activity visible only in memory.
Why use it?
It helps preserve and analyze evidence that may disappear when an affected computer is shut down.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the 1ai-skills plugin — 209 skills, 4 commands shipped together

Good fit Use it during incident response to investigate process injection, fileless malware, credential theft, rootkits, and other activity visible only in memory.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/oyi77/1ai-skills/conducting-memory-forensics-with-volatility
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add oyi77/1ai-skills --skill conducting-memory-forensics-with-volatility
Clone the repo
git clone --depth 1 https://github.com/oyi77/1ai-skills

Made for: Claude Code.

Or install 1ai-skills, the plugin that ships this one along with the rest of its 209 skills, 4 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for conducting-memory-forensics-with-volatility

README.md
[![agentmods](https://agentmods.dev/badge/skills/oyi77/1ai-skills/conducting-memory-forensics-with-volatility/github.svg)](https://agentmods.dev/skills/oyi77/1ai-skills/conducting-memory-forensics-with-volatility)
Your own site
<a href="https://agentmods.dev/skills/oyi77/1ai-skills/conducting-memory-forensics-with-volatility"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/conducting-memory-forensics-with-volatility/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for conducting-memory-forensics-with-volatility

Your own site · 80×15
<a href="https://agentmods.dev/skills/oyi77/1ai-skills/conducting-memory-forensics-with-volatility"><img src="https://agentmods.dev/badge/skills/oyi77/1ai-skills/conducting-memory-forensics-with-volatility.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 88 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,088 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high YARA Match · line 48
    YARA rule matched a known malware signature (reverse shell, backdoor, ransomware, C2 framework, or info stealer).
    Fix: Remove the malware payload or compromised file entirely. Investigate how it entered the skill and audit all other artifacts for additional indicators of compromise.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00088 $0.01088
Opus 5 $0.00044 $0.00544
Sonnet 5 $0.00018 $0.00218
Haiku 4.5 $0.00009 $0.00109

Measured 7d ago against content hash 58cd134a6e24, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

conducting-memory-forensics-with-volatility scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

cybersecurity/_deprecated/conducting-memory-forensics-with-volatility/SKILL.md · 122 lines

How it starts

The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Conducting Memory Forensics With Volatility

Overview

Cybersecurity skill for conducting memory forensics with volatility. Follows industry best practices and security standards.

When to Use

Trigger phrases:

  • "conducting memory forensics with volatility"

  • "Performs memory forensics analysis using Volatility 3 to extract evidence of mal"

  • An endpoint has been contained during an active incident and volatile evidence must be preserved

  • EDR alerts suggest process injection or fileless malware that only exists in memory

  • Encryption keys need to be recovered from a ransomware-infected system before shutdown

  • Credential theft (Mimikatz, LSASS dumping) is suspected and evidence must be confirmed

  • A rootkit or kernel-level compromise is suspected and disk-based analysis is insufficient

Do not use for analyzing disk images or file system artifacts; use disk forensics tools (Autopsy, FTK) for those tasks.

When NOT to Use

  • When you lack proper authorization for testing
  • For production systems without change management
  • When the task requires legal or compliance expertise beyond technical scope

Prerequisites

  • Memory acquisition tool deployed or available: WinPmem, Magnet RAM Capture, DumpIt, or AVML (Linux)
  • Volatility 3 installed with Python 3.8+ and required symbol tables
  • Sufficient storage for memory dumps (equal to system RAM size, typically 8-64 GB)
  • YARA rules for malware detection in memory (Florian Roth's signature-base, custom rules)
  • Reference baseline of normal processes and DLLs for the OS version being analyzed
  • Chain of custody documentation for evidence handling

Workflow

# Example: IOC detection
import re

IOC_PATTERNS = {
    "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
    "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
    "hash_md5": r"\b[a-f0-9]{32}\b",
    "hash_sha256": r"\b[a-f0-9]{64}\b",
}

def extract_iocs(text: str) -> dict:
    return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
  1. Scope the Analysis — Define what memory forensics artifacts or data sources to examine and the investigation timeline.
  2. Preserve Evidence — Create forensic copies of relevant data. Maintain chain of custody documentation.
  3. Extract Key Indicators — Use volatility to parse and extract relevant memory forensics data points from collected artifacts.
  4. Correlate Findings — Cross-reference extracted data with other sources (threat intel, logs, timelines).
  5. Build Timeline — Construct a chronological sequence of events related to memory forensics.
  6. Document Analysis — Write findings report with evidence, conclusions, and recommendations.

Read the full file on GitHub · 122 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 7d ago First seen · 122 lines · 88 tokens per session scan A 58cd134a6e24

Subscribe to this mod's changes

conducting-memory-forensics-with-volatility is a skill published in the GitHub repository oyi77/1ai-skills (12 stars, last pushed today), licensed MIT. It adds 88 tokens to every session and 1,088 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.

Related

Other skills, from other repositories

conducting-memory-forensics-with-volatility

Performs memory forensics analysis using Volatility 3 to extract evidence of malware execution, process injection, network connections, and credential theft from RAM dumps captured during incident response. Covers memory acquisition, process analysis, DLL inspection, and malware detection. Activates for requests…

26zl/cybersec-toolkit · 87 tokens

conducting-memory-forensics-with-volatility

Performs memory forensics analysis using Volatility 3 to extract evidence of malware execution, process injection, network connections, and credential theft from RAM dumps captured during incident response. Covers memory acquisition, process analysis, DLL inspection, and malware detection. Activates for requests…

Youngmaidainon/Agent-Level-Up · 87 tokens

conducting-memory-forensics-with-volatility

Performs memory forensics analysis using Volatility 3 to extract evidence of malware execution, process injection, network connections, and credential theft from RAM dumps captured during incident response. Covers memory acquisition, process analysis, DLL inspection, and malware detection. Activates for requests…

RobotFlow-Labs/skills-repo · 87 tokens

analyzing-memory-dumps-with-volatility

Analyzes RAM memory dumps from compromised systems using the Volatility framework to identify malicious processes, injected code, network connections, loaded modules, and extracted credentials. Supports Windows, Linux, and macOS memory forensics. Activates for requests involving memory forensics, RAM analysis…

mukul975/Anthropic-Cybersecurity-Skills · 80 tokens

detecting-process-injection-in-memory

Detects process injection in a memory image by identifying private executable regions with no file backing, RWX protections, and modified entry points using Volatility 3 malfind-style analysis. Activates for requests to detect process injection, find injected code in memory, or triage suspicious executable regions in…

meltedinhex/analyst-ai-pack · 70 tokens

analyzing-memory-dumps-with-volatility

Analyzes RAM memory dumps from compromised systems using the Volatility framework to identify malicious processes, injected code, network connections, loaded modules, and extracted credentials. Supports Windows, Linux, and macOS memory forensics. Activates for requests involving memory forensics, RAM analysis…

26zl/cybersec-toolkit · 80 tokens