Agentic Malware Analysis
Description
Agentic malware analysis environment with MCP-connected disassemblers, RE tooling, and structured workflows for Claude Code and Codex CLI.
Installation
claude install-skill https://github.com/mrphrazer/agentic-malware-analysis README
Agentic Malware Analysis
Automated deep malware reverse engineering driven by AI agents. A Kali-based Docker environment pairs 50+ RE tools with MCP-connected disassembler backends ([Binary Ninja][binary-ninja-headless-mcp] or [Ghidra][ghidra-headless-mcp]) and a structured multi-phase orchestrator skill that turns a raw binary into a case directory of ranked evidence, validated hypotheses, component maps, and a prioritized deep-analysis plan -- with no human interaction required. Ready for [Claude Code][claude-code] and [Codex CLI][codex-cli].
See the companion blog post [Building a Pipeline for Agentic Malware Analysis][blog-post] for background, a case study, and evaluation.
Why
Initial malware analysis involves a number of routine steps: collecting hashes and compiler artifacts, extracting strings, inspecting imports, running YARA and capa, correlating the results, and identifying code areas for closer inspection. These steps provide the basis for deeper analysis, but they are often repetitive and time-consuming.
This repository automates much of that workflow. The orchestrator skill collects and organizes analysis artifacts, highlights relevant signals, generates evidence-backed hypotheses, builds a basic component model, and prepares a prioritized deep-analysis plan. All intermediate results are stored in a per-sample case directory on disk, making the workflow easier to resume and review.
Via MCP, the agent can also use Binary Ninja or Ghidra to inspect functions, follow cross-references, and tie findings to concrete code locations. The result is a structured starting point for follow-up analysis rather than ad hoc triage alone.
Features
- undefined
Prerequisites
- undefined
Quick Start
**Important:** `run_docker.sh` mounts your current working directory into the container at `/agent`. The agent wrappers run with full permissions (`--dangerously-skip-permissions` / `--dangerously-bypass-approvals-and-sandbox`) by design, so the agent can read, write, and execute anything in that directory. Clone the repository into a dedicated directory and place only the files you want the agent to access there.
git clone https://gith
Related Agents
hooks:
--- <role> You are a GSD codebase mapper. You explore a codebase for a specific focus area and write analysis documents directly to `.planning/codebase/`. You are spawned by `/gsd:map-codebase` with o
Research community attack-tree-construction
| Systematic attack path visualization and analysis. | - | [wshobson/agents](https://github.com/wshobson/agents) |
Research community Error Analysis
| You are an expert error analysis specialist with deep expertise in debugging distributed systems, an... | - | [wshobson/agents](https://github.com/wshobson/agents) |
Research community Improve Agent
| Systematic improvement of existing agents through performance analysis, prompt engineering, and cont... | - | [wshobson/agents](https://github.com/wshobson/agents) |
Research community Market Opportunity
| Generate a comprehensive market opportunity analysis for a startup, including Total Addressable Mark... | - | [wshobson/agents](https://github.com/wshobson/agents) |
Research community market-sizing-analysis
| Comprehensive market sizing methodologies for calculating Total Addressable Market (TAM), Serviceabl... | - | [wshobson/agents](https://github.com/wshobson/agents) |
Research community