Community
Volatility plugins developed and maintained by the community
Install / Use
/learn @volatilityfoundation/CommunityREADME
community
Volatility plugins developed and maintained by the community. See the README file inside each author's subdirectory for a link to their respective GitHub profile page where you can find usage instructions, dependencies, license information, and future updates for the plugins.
usage
- Git clone the Volatility repository or Download a Release
- Git clone this repository to $PLUGINSPATH
- Pass the --plugins=$PLUGINSPATH option to Volatility when you run it (see Specifying Additional Plugin Directories)
NOTE: If you pass the root of the $PLUGINSPATH directory, then all plugins will recursively be loaded. Its possible that plugins may try to register the same command line options and produce a conflict. If this happens, just point --plugins at one or more specific subdirectories (: separated on Linux/Mac or ; separated on Windows).
disclaimer
These plugins are written by various authors and collected from the authors' GitHub repositories, websites and blogs at a particular point in time. We don't guarantee that the plugins you download from this repo will be the most recent ones published by the individual authors, that they're compatible with the most recent version of Volatility, or that they report results accurately.
contributing
The best way to contribute is to fork the repository, add or modify plugins, and then submit a pull request.
frameworks
Researchers and developers in the community have also created frameworks that build on top of Volatility. These aren't necessarily Volatility plugins (that you would import with --plugins) and usually they contain additional modules, configurations, and components. For that reason, we don't feature those frameworks in this repository, but we'd still like to reference them:
- Autopsy Plugins by Mark McKinnon
- PyREBox by Xabier Ugarte-Pedrero at Cisco Talos
- Cuckoo Sandbox uses Volatility for its Memory module
- VolDiff Malware Memory Footprint Analysis by @aim4r
- Evolve Web interface for the Volatility Memory Forensics Framework by James Habben
- GVol Lightweight GUI (Java) by EG-CERT
- LibVMI Simplified Virtual Machine Introspection
- DAMM Differencial Analysis of Malware in Memory
- YaraVol GUI for Volatility Framework and Yara
- VolUtility Web Interface for Volatility by Kevin Breen
- ROPMEMU A framework to analyze, dissect and decompile complex code-reuse attacks by Mariano Graziano
- VolatilityBot An automated memory analyzer for malware samples and memory dumps by Martin Korman
- ProfileScan Profile detection for Volatility by Stanislas Lejay (P1kachu)
Don't see your project here? Let us know by submitting a pull request, creating an issue, or tweet us at @volatility.
Related Skills
node-connect
341.0kDiagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps
claude-opus-4-5-migration
84.4kMigrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5
frontend-design
84.4kCreate distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
model-usage
341.0kUse CodexBar CLI local cost usage to summarize per-model usage for Codex or Claude, including the current (most recent) model or a full model breakdown. Trigger when asked for model-level usage/cost data from codexbar, or when you need a scriptable per-model summary from codexbar cost JSON.
