A secure sandbox environment for malware developers and red teamers to test payloads against detection mechanisms before deployment. Integrates with LLM agents via MCP for enhanced analysis capabilities.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"litterbox": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in security
Proof primitive for AI agents on MultiversX. Anchor file hashes on-chain as verifiable proofs.
Model Context Protocol for WinDBG
Security scanner for GitHub repos, Agent Skills, Plugins, and MCP servers. 18 scanners. Zero dependencies.
AI agent trust & reputation protocol — verify, score, route, compare, delegate. 18 tools.
MCP Security Weekly
Get CVE alerts and security updates for LitterBox and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.

A self-hosted payload-analysis sandbox for red teams. Upload a sample, run static / dynamic / EDR analysis against it, get a Detection Score and a triggering-indicators breakdown — decide whether the payload is field-ready before it leaves the lab.
LitterBox can also dispatch payloads to a separate EDR-instrumented Windows VM (Elastic Defend or Fibratus) and pull the correlated detection alerts back into the results page.
While designed primarily for red teams, LitterBox is equally useful for blue teams running the same tools in their malware-analysis workflows.
Operator and developer documentation lives in the LitterBox Wiki.
| Topic | Wiki page |
|---|---|
| How everything fits together | Application Architecture |
| Run static + every reachable EDR in parallel | All in One Pipeline |
| Dispatch payloads to a real EDR VM | EDR Integration → Elastic Defend / Fibratus |
| Whiskers agent (install, endpoints, build) | Whiskers Agent |
| Every HTTP endpoint | HTTP API Reference |
| CLI / Python lib / MCP for LLMs | GrumpyCats CLI · GrumpyCats Library · LitterBoxMCP |
| What feeds the Detection Score | Detection Score Explained |
| Configure scanners / paths / timeouts | Configuration Reference |
| Add custom YARA rules / scanners | YARA Rules Management · New Scanner |
git clone https://github.com/BlackSnufkin/LitterBox.git
cd LitterBox
python -m venv venv
.\venv\Scripts\Activate.ps1
pip install -r requirements.txt
python litterbox.py # add --debug for verbose logging
Open http://127.0.0.1:1337. Requires Python 3.11+ and an admin shell.
git clone https://github.com/BlackSnufkin/LitterBox.git
cd LitterBox/Docker
chmod +x setup.sh
./setup.sh
The setup script provisions a Windows 10 container with KVM and runs LitterBox inside. Initial build takes ~1 hour.
http://localhost:8006localhost:3389 (creds in the docker compose file)http://127.0.0.1:1337 once setup completesDrop one or more profile YAMLs under Config/edr_profiles/ and the upload page picks them up at boot. Full walkthroughs in the wiki: Whiskers Agent → Elastic Defend Setup or Fibratus Setup.
Bundled binaries under Scanners/. Versions and last-update dates tracked here so operators can tell at a glance whether a scanner is current.
| Scanner | Version | Last updated | Source |
|---|---|---|---|
| PE-Sieve | 0.4.1.2 (f1dc39d) | 2026-05-02 | hashe |