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
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionextracting-memory-artifacts-with-rekallExecute the skills CLI command in your project's root directory to begin installation:
Fetches extracting-memory-artifacts-with-rekall from mukul975/Anthropic-Cybersecurity-Skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate extracting-memory-artifacts-with-rekall. Access via /extracting-memory-artifacts-with-rekall in your agent's command palette.
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.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
8.6K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
8.6K
stars
| 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 |
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:
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}")
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
mukul975/Anthropic-Cybersecurity-Skills
Solid pick for teams standardizing on skills: extracting-memory-artifacts-with-rekall is focused, and the summary matches what you get after install.
extracting-memory-artifacts-with-rekall fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
We added extracting-memory-artifacts-with-rekall from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Registry listing for extracting-memory-artifacts-with-rekall matched our evaluation — installs cleanly and behaves as described in the markdown.
extracting-memory-artifacts-with-rekall has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in extracting-memory-artifacts-with-rekall — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in extracting-memory-artifacts-with-rekall — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for extracting-memory-artifacts-with-rekall matched our evaluation — installs cleanly and behaves as described in the markdown.
extracting-memory-artifacts-with-rekall is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
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