Mulder takes a directory of forensic evidence (disk images, memory dumps, PCAPs, event logs) and runs a five-phase autonomous investigation with hard quality gates between each phase. It produces structured incident reports with MITRE ATT&CK mappings, IOC exports, and a full audit trail. An adversarial "Alternative Narrative" phase challenges every finding before the report is generated. All tool invocations go through typed MCP interfaces - never through a shell - and an append-only audit log validates every evidence citation at the API boundary, making findings with fabricated evidence citations structurally impossible to submit.

Results

Four autonomous investigations against real forensic datasets, unmodified from tool output. Each case has an interactive HTML report on GitHub Pages (sidebar navigation, dark/light theme, audit trail). See the examples index for all report links.

The NIST Data Leakage case has a detailed accuracy report validated against published NIST ground truth: 60% full match, 90% detection rate, 5% false positive rate. The single false positive involved incorrect causal attribution (blaming CCleaner for artifact destruction when the answer key confirms it was launched and closed without action).

How It Works

Each investigation runs through five phases with quality gates between them. Phases 2-4 use a plan-and-execute pipeline with three specialized roles (planner, executor, analyst) that can optionally be assigned to different models for cost optimization.

1. Catalog - scan evidence directory, classify file types, identify distinct systems
2. Extraction - run applicable forensic tools per system, index results into FTS5 database
3. Cross-System Analysis - correlate events across systems, map MITRE ATT&CK techniques, deduplicate findings
4. Alternative Narrative - challenge the primary narrative with counter-evidence, test alternative hypotheses, audit for tool and evidence coverage gaps
5. Report - write the investigation narrative, generate Markdown/HTML reports, export IOCs and ATT&CK Navigator layers

Each gate validates structural criteria (minimum sources indexed, findings submitted, MITRE mappings present, audit tools invoked). Failed gates trigger bounded phase retries; single-agent retries include gap-specific remediation instructions. See Architecture for the full pipeline design.

Key Design Decisions

No shell access, no built-in tools. All 140+ tool invocations go through typed MCP interfaces with validated parameters. Every Claude Code built-in tool (Bash, Read, Grep, Glob, Write, Edit, WebFetch, WebSearch, ...) is disabled for every agent session, so the agent never gets a shell, never reads evidence or writes the workspace outside the audit log, and never reaches the network. Every action is auditable and every parameter is constrained to its declared type.

Anti-hallucination at the API boundary. Every finding must cite evidence_refs that are real tool_call_id values from the append-only audit log. The MCP server validates these references at submission time and rejects findings that cite nonexistent tool calls. Timestamps are validated as ISO-8601 and auto-nullified when they appear fabricated. This is enforced architecturally, not by prompting.

Adversarial self-review. Phase 4 explicitly challenges the primary narrative before report generation. It formulates counter-hypotheses, searches for disconfirming evidence, and runs coverage audits to identify which tools were applicable but never invoked and which evidence sources were indexed but never cited.

Token efficiency. The SRL-2018 investigation (11 systems, 120 GB, 1,508 tool calls across 336 minutes) consumed 698K tokens. For cost optimization, the three pipeline roles (planner, executor, analyst) can be assigned to different models - routing mechanical tool-calling to a cheaper model while preserving reasoning quality for analysis.

Quick Start

Install natively (SIFT Workstation, Debian/Ubuntu)

sudo apt install git sleuthkit yara p7zip-full binutils
pipx install "mulder-dfir[forensics]"
mulder setup
mulder investigate /path/to/evidence my-case-id

pipx installs mulder into its own isolated virtualenv and puts the mulder command on your PATH; uv tool install "mulder-dfir[forensics]" works identically. The forensics extra pulls in Zircolite's runtime dependencies. If mulder is not found afterwards, open a new terminal — Ubuntu only adds ~/.local/bin to PATH at login, and only if it already existed.

On first run mulder creates a working directory at ~/.mulder/workspace (override with --cwd or MULDER_CWD) and writes a default .mcp.json into it. Case databases and reports go to ~/.mulder/cases (override with --db-dir).

mulder setup downloads everything mulder owns - rule sets, signatures, and helper binaries - in one run (~2.2 GB, no sudo, refuses to run as root). It pins the same versions the container image uses. The rest of the forensic toolchain (Sleuth Kit, plaso, Zeek, dotnet) is your OS's job; SIFT already provides all of it except the yara binary above. See the Usage Guide for the full picture. The container remains available if you would rather not install anything at all.

Run with Docker (everything preinstalled)

docker pull ghcr.io/calebevans/mulder:1.5.2

mkdir -p ~/mulder-cases

docker run -it --privileged \
  -v /path/to/evidence:/evidence:ro \
  -v ~/mulder-cases:/home/mulder/.mulder/cases \
  -e ANTHROPIC_API_KEY=$ANTHROPIC_API_KEY \
  ghcr.io/calebevans/mulder:1.5.2

mulder investigate /evidence my-case-id

For Vertex AI, Amazon Bedrock, non-Anthropic models via LiteLLM, and full CLI options, see the Usage Guide.

Use as an MCP server

Add to claude_desktop_config.json / .mcp.json:

{
  "mcpServers": {
    "mulder": {
      "type": "stdio",
      "command": "mulder",
      "args": ["serve"]
    }
  }
}

Without installing first, uvx mulder-dfir serve works too.

Case Briefing (Optional)

Drop a MULDER.md file in your evidence directory to provide case context:

## What We Know
- The network was breached on March 15
- Suspect account: jsmith

## What We're Looking For
- How did the attacker gain initial access?
- Was data exfiltrated?

The briefing is injected into every investigation phase, guiding tool selection, analysis focus, and report framing. See the Usage Guide for details.

Forensic Tools

Mulder integrates 35+ open-source forensic tools exposed as 140+ typed MCP operations:

* Detect-It-Easy is supported but not bundled: its .deb pulls in ten libqt5* packages for a CLI that draws nothing. run_detect_it_easy uses it if diec is on $PATH, and reports it as missing otherwise. Packing is still flagged without it — triage_binary checks section entropy, RWX permissions, known packer section names and import-table shape.

Full API reference: Tool Manifest

Output

Each investigation produces:

• Markdown and HTML reports - executive summary, attack timeline, findings with MITRE ATT&CK mappings, IOC tables, and audit trail (example HTML reports)
• Per-case SQLite database - FTS5 full-text search across all indexed evidence
• Append-only audit log - JSONL recording every tool invocation with BLAKE2b output hashes
• Optional exports - STIX 2.1 IOC bundle, CSV IOC list, and MITRE ATT&CK Navigator layer via mulder export-iocs and mulder export-navigator

Documentation

License

Apache-2.0