More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Memory Forensics: Investigate RAM Captures with Volatility

    1

    Investigate RAM captures with Volatility: acquire cleanly, survey processes and network, detect injection and rootkits, build a defensible timeline.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Memory Forensics: Investigate RAM Captures with Volatility

    Memory Forensics: Investigate RAM Captures with Volatility

    Example session with this skill installed

    We have a memory image from a workstation that may be compromised. Walk me through the investigation and give me a timeline I can defend.

    • Read your context and instructions
    • Compiled the memory forensics

    Acquisition: verified the image first — 16 GB, captured with the standard tool, hash recorded, and the capture window noted so timestamps near it are treated skeptically. Checked the Volatility profile matched the OS build before running anything; a wrong profile produces confident garbage. Survey: pslist showed 87 processes, and one stood out immediately — a process named for a system service running from a temp folder, with no on-disk binary at that path. Netscan showed an established connection to an external address on port 443, with no matching entry in the firewall logs. Hunt: malfind flagged injected code in the suspect process — executable memory with no file backing. Psxview showed the process hidden from one of the three listings, a classic hiding sign. Checked for rootkit hooks with the driver scan; one unsigned driver loaded from the same temp folder. Extract: strings over the process memory recovered a URL, a username, and a partial credential — the credential was partial because that region was encrypted in memory, which the report states plainly instead of guessing at it. YARA over memory matched a known fileless payload family. Timeline: timeliner merged process creation, registry writes, network events, and file activity into one CSV. The story reads cleanly: initial access via a document at 09:14, process injection at 09:17, persistence via a Run key at 09:19, first C2 connection at 09:21. Validation: every finding was confirmed through a second method — the hidden process through psxview and pslist, the injection through malfind and a manual memory-map read, the C2 through netscan and the firewall logs. The report leads with the attack narrative, attaches raw plugin outputs, and states explicitly what was not found where it was looked for.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Disk forensics tells you what was stored. Memory forensics tells you what was running — including the fileless payloads that never touched disk, the injected code that lives only in a process, and the credentials still sitting in RAM. This skill covers acquiring a memory capture cleanly, surveying processes and network state, hunting injection, hiding, and persistence, extracting credentials and strings, and correlating findings into a timeline that holds up. The discipline is validation: every finding goes through a second plugin or method before it reaches the report, because memory forensics has a proud tradition of artifacts that turn out to be parser bugs.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Security.

    It covers memory analysis, not disk or network forensics — the timeline needs those too, and the skill shows how to cross-reference them.
    Memory changes during acquisition, so timestamps near the capture window are treated skeptically.
    Encrypted regions are legitimately unreadable; not every unreadable blob is malicious, and the skill says so rather than inventing content.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 3 days ago

    Permissions

    Terminal / Shell
    Listed3 days ago

    What's inside

    Frequently Asked Questions

    Match it to the OS build of the captured machine. A wrong profile produces confident garbage — processes that never existed, addresses that mean nothing. Verify before running anything.

    Fileless until proven otherwise. Check the memory maps for injected code, look for the parent process, and cross-reference the disk — but do not assume it is malicious on that fact alone.

    No. Validate every finding through a second plugin or method before it goes in the report. Memory forensics has a long history of artifacts that turn out to be parser bugs.

    New in Security