LitterBox - A self-hosted sandbox for red teams to test payloa

项目说明

LitterBox

!LitterBox Logo

![Python]()
![Windows]()
![Linux]()
![Docker]()
![MCP]()
![Ask DeepWiki]()
![GitHub Stars]()

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 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.

Documentation

Operator and de documentation lives in the LitterBox Wiki.

| Topic | Wiki page |
|---|---|
| How e 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 |

Installation

Windows

Open . Requires Python 3.11+ and an admin shell.

Linux (Docker)

The setup script pro a Windows 10 container with KVM and runs LitterBox inside. Initial build takes ~1 hour.

EDR setup (optional)

Drop 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.

Scanners

Bundled binaries under Scanners/. and last-update dates tracked here so operators can tell at a glance whether a scanner is current.

| Scanner | | Last updated | Source |
|---|---|---|---|
| PE-Sieve | 0.4.1.2 (f1dc39d) | 2026-05-02 | hasherezade/pe-sieve |
| Hollows-Hunter | 0.4.1.2 (e271f7e) | 2026-04-18 | hasherezade/hollows_hunter |
| Moneta | 5b65395 | 2024-03-16 | forrest-orr/moneta |
| Patriot | — | 2024-12-29 | joe-desimone/patriot |
| Hunt-Sleeping-Beacons | 84dd3a9 | 2026-01-25 | thefLink/Hunt-Sleeping-Beacons |
| RedEdr | 3bd6b97 (EXE-only build) | 2026-05-03 | dobin/RedEdr |
| YARA (engine yara64.exe) | — | 2024-12-29 | /yara |
| Elastic YARA rules (Scanners/Yara/rules/elastic-yara/) | d131ea8 | 2026-04-30 | elastic/protections-artifacts |
| YARA-Forge Extended (Scanners/Yara/rules/YARAForge/) | 0.9.1 (release 20260503) | 2026-05-03 | YARAHQ/yara-forge |
| CheckPlz | — | 2024-12-29 | BlackSnufkin/CheckPlz |
| Stringnalyzer | — | 2025-01-27 | BlackSnufkin/Rusty-Playground |
| HolyGrail | — | 2025-08-18 | BlackSnufkin/HolyGrail |

format: <release-> or <release-> (release) when the binary is pulled from an upstream release; <release-> (\<commit>\) or just \<commit>\` when built from source. Last-updated date is the upstream commit / release date, not the local build date.

When you refresh a scanner: replace the binary under its Scanners/<Name>/` directory and update the row abo + date).

Contributing

See CONTRIBUTING.md. Work in feature branches on personal forks.

Support 🍺

<a href=" src=" width="200" height="60"></a>

![Stars]()

Security Ad

Acknowledgments

LitterBox stands on the work of these projects and their authors:

| Tool | Author |
|---|---|
| YARA rules · Elastic Defend | Elastic Security |
| PE-Sieve · Hollows-Hunter | hasherezade |
| Moneta | Forrest Orr |
| Patriot | joe-desimone |
| Hunt-Sleeping-Beacons | thefLink |
| RedEdr | dobin |
| Fibratus | rabbitstack |
| ThreatCheck (basis for CheckPlz) | rasta-mouse |
| MalAPI reference DB | mr.d0x |

Interface

!LitterBox Demo

项目信息

开发语言：YARA

Star 数：1544

技术要点

该项目属于黑客技术方向的开源资源，代码结构清晰，适合安全研究人员学习参考。项目围绕A self-hosted sandbox for red teams to test payloads against modern detection before deployment. MCP integration lets an LLM agent dri end to end.展开，提供了可运行的实现，对理解相关安全机制、工具原理与攻防技术具有较高的研究价值。

从技术实现角度看，此类项目的核心在于对底层原理的深入理解与工程化落地。开发者在研究过程中可以结合官方文档与社区讨论，梳理项目的初始化流程、核心模块职责与数据流转，逐步掌握其中的技术细节与设计思路。

使用与学习建议

1. 下载源码压缩包，解压到本地环境。

2. 根据项目类型准备对应的运行环境与依赖。

3. 按照 README 中的步骤完成配置与部署。

4. 在隔离的测试环境中运行验证，避免影响生产系统。

免责声明

本资源来源于开源社区，仅供安全研究、技术学习与合法授权范围内的攻防演练使用，请勿用于任何非法或侵害他人权益的用途。使用本项目产生的一切后果由使用者自行承担。