extracting-memory-artifacts-with-rekall

Uses Rekall memory forensics framework to analyze memory dumps for process hollowing, injected code via VAD anomalies, hidden processes, and rootkit detection. Applies plugins like pslist, psscan, vadinfo, malfind, and dlllist to extract forensic artifacts from Windows memory images. Use during incident response memory analysis.

Works with

Claude CodeCursorClineWindsurfCodexGooseGitHub CopilotZed

0

total installs

0

this week

8.6K

GitHub stars

0

upvotes

Install Skill

Run in your terminal

$npx skills install mukul975/Anthropic-Cybersecurity-Skills/extracting-memory-artifacts-with-rekall

0

installs

0

this week

8.6K

stars

Installation Guide

How to use extracting-memory-artifacts-with-rekall on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • Cursor installed and configured on your machine
  • Node.js 16+ with npm — verify with node --version
  • Active project directory where you want to add extracting-memory-artifacts-with-rekall
2

Run the install command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills install mukul975/Anthropic-Cybersecurity-Skills/extracting-memory-artifacts-with-rekall

Fetches extracting-memory-artifacts-with-rekall from mukul975/Anthropic-Cybersecurity-Skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI shows a list of agents. Use arrow keys and space to select Cursor:

◆ Which agents do you want to install to?
│ ── Universal (.agents/skills) ────────────────
│ · Cline · Codex · Goose · Windsurf
│ ●Cursor(selected)
│ · Cursor · Aider · Continue
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/extracting-memory-artifacts-with-rekall

Restart Cursor to activate extracting-memory-artifacts-with-rekall. Access via /extracting-memory-artifacts-with-rekall in your agent's command palette.

Security Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.

Documentation

name
extracting-memory-artifacts-with-rekall
description
'Uses Rekall memory forensics framework to analyze memory dumps for process hollowing, injected code via VAD anomalies, hidden processes, and rootkit detection. Applies plugins like pslist, psscan, vadinfo, malfind, and dlllist to extract forensic artifacts from Windows memory images. Use during incident response memory analysis. '
domain
cybersecurity
subdomain
security-operations
tags
- extracting - memory - artifacts - with
version
'1.0'
author
mahipal
license
Apache-2.0
nist_csf
- DE.CM-01 - RS.MA-01 - GV.OV-01 - DE.AE-02

Extracting Memory Artifacts with Rekall

When to Use

  • When performing authorized security testing that involves extracting memory artifacts with rekall
  • When analyzing malware samples or attack artifacts in a controlled environment
  • When conducting red team exercises or penetration testing engagements
  • When building detection capabilities based on offensive technique understanding

Prerequisites

  • Familiarity with security operations concepts and tools
  • Access to a test or lab environment for safe execution
  • Python 3.8+ with required dependencies installed
  • Appropriate authorization for any testing activities

Instructions

Use Rekall to analyze memory dumps for signs of compromise including process injection, hidden processes, and suspicious network connections.

from rekall import session
from rekall import plugins

# Create a Rekall session with a memory image
s = session.Session(
    filename="/path/to/memory.raw",
    autodetect=["rsds"],
    profile_path=["https://github.com/google/rekall-profiles/raw/master"]
)

# List processes
for proc in s.plugins.pslist():
    print(proc)

# Detect injected code
for result in s.plugins.malfind():
    print(result)

Key analysis steps:

  1. Load memory image and auto-detect profile
  2. Run pslist and psscan to find hidden processes
  3. Use malfind to detect injected/hollowed code in process VADs
  4. Examine network connections with netscan
  5. Extract suspicious DLLs and drivers with dlllist/modules

Examples

from rekall import session
s = session.Session(filename="memory.raw")
# Compare pslist vs psscan for hidden processes
pslist_pids = set(p.pid for p in s.plugins.pslist())
psscan_pids = set(p.pid for p in s.plugins.psscan())
hidden = psscan_pids - pslist_pids
print(f"Hidden PIDs: {hidden}")

List & Monetize Your Skill

Submit your Claude Code skill and start earning

Get started →

Use Cases

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

Improve work quality by 30-40% with less effort

Implementation Guide

Prerequisites

  • Claude Desktop or compatible AI client with skill support
  • Clear understanding of task or problem to solve
  • Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Steps

  1. 1Install skill using provided installation command
  2. 2Test with simple use case relevant to your work
  3. 3Evaluate output quality and relevance
  4. 4Iterate on prompts to improve results
  5. 5Integrate into regular workflow if valuable

Common Pitfalls

  • Expecting perfect results without iteration
  • Not providing enough context in prompts
  • Using skill for tasks outside its intended scope
  • Accepting outputs without review and validation

Best Practices

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • Don't use without understanding skill limitations
  • Don't skip validation of outputs
  • Don't share sensitive information in prompts
  • Don't expect skill to replace human judgment

💡 Pro Tips

  • Be specific about desired format and style
  • Ask for multiple options to choose from
  • Request explanations to understand reasoning
  • Combine AI efficiency with human expertise

When to Use This

✓ Use when

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid when

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Related Skills

Reviews

4.455 reviews
  • H
    Harper DixitDec 24, 2024

    Solid pick for teams standardizing on skills: extracting-memory-artifacts-with-rekall is focused, and the summary matches what you get after install.

  • P
    Pratham WareDec 20, 2024

    extracting-memory-artifacts-with-rekall fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.

  • I
    Ira MenonDec 16, 2024

    We added extracting-memory-artifacts-with-rekall from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.

  • H
    Harper NasserDec 8, 2024

    Registry listing for extracting-memory-artifacts-with-rekall matched our evaluation — installs cleanly and behaves as described in the markdown.

  • I
    Ira SanchezDec 8, 2024

    extracting-memory-artifacts-with-rekall has been reliable in day-to-day use. Documentation quality is above average for community skills.

  • K
    Kofi GuptaDec 8, 2024

    Useful defaults in extracting-memory-artifacts-with-rekall — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • I
    Ira RaoNov 27, 2024

    Useful defaults in extracting-memory-artifacts-with-rekall — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • X
    Xiao SanchezNov 27, 2024

    Registry listing for extracting-memory-artifacts-with-rekall matched our evaluation — installs cleanly and behaves as described in the markdown.

  • S
    Sakshi PatilNov 11, 2024

    extracting-memory-artifacts-with-rekall is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • S
    Sofia FarahNov 11, 2024

    Solid pick for teams standardizing on skills: extracting-memory-artifacts-with-rekall is focused, and the summary matches what you get after install.

showing 1-10 of 55

1 / 6

Discussion

Comments — not star reviews
  • No comments yet — start the thread.