nzyuko/fox3 — explained in plain English
Analysis updated 2026-08-08 · repo last pushed 2026-06-03
Run a red team operation by deploying agents on Windows workstations and managing them through a web dashboard.
Conduct penetration testing by sending encrypted task commands to agents and receiving results in real time.
Simulate attacks in enterprise environments using multiple network listener types like HTTP/2 and HTTP/3.
| nzyuko/fox3 | awlx/packetyeeter | huey1in/kiroclaim | |
|---|---|---|---|
| Stars | 13 | 13 | 13 |
| Language | Go | Go | Go |
| Last pushed | 2026-06-03 | — | — |
| Maintenance | Maintained | — | — |
| Setup difficulty | moderate | hard | moderate |
| Complexity | 4/5 | 5/5 | 3/5 |
| Audience | researcher | ops devops | ops devops |
Figures from each repo's GitHub metadata at analysis time.
Requires understanding of C2 concepts and network listeners, some advanced modules are Windows-only and the project is actively in development.
fox3 is a command-and-control (C2) server, which is the backend tooling used in red team and penetration testing operations. In plain terms, security professionals use it to manage "agents", small programs they've deployed on a target machine, so they can send those agents tasks and receive results back, all through a web browser interface instead of a traditional command line. The way it works is straightforward at a high level. An agent on a target machine sends an encrypted message to a "listener" (a server endpoint waiting for check-ins). The server decrypts the message, queues up any pending jobs for that agent, and sends those jobs back in the same response. Meanwhile, the person running the operation (the operator) watches everything through a React-based web dashboard that updates in real time. All communication between agent and server is encrypted, and there's no command-line interface for the operator, the browser console is the only way to interact with it. This is built for security researchers, red teams, and penetration testers who need a lightweight way to manage compromised machines during a simulated attack. For example, a red team operator might deploy an agent on a Windows workstation, then use the web dashboard to tell that agent to run commands, grab data, or maintain access. The project currently supports several types of network listeners (HTTP/1.1, HTTP/2, H2C, HTTP/3), with more traditional channels like TCP, DNS, and SMB listed as coming soon. A few notable design choices stand out. The project uses SQLite for storing state, which keeps things simple and self-contained rather than requiring a separate database server. It's written in Go for the backend with a React frontend. Some advanced modules are Windows-only, which makes sense given that Windows is the most common target in enterprise environments. The project is actively in development and is licensed under GPLv3.
A command-and-control server for red team and penetration testing operations. Operators manage deployed agents on target machines through a real-time web dashboard, sending tasks and receiving encrypted results.
Mainly Go. The stack also includes Go, React, SQLite.
Maintained — commit in last 6 months (last push 2026-06-03).
Free to use and modify, but any distributed software must also be open-sourced under the same GPL license.
Setup difficulty is rated moderate, with roughly 1h+ to a first successful run.
Mainly researcher.
This repo across BitVibe Labs
Verify against the repo before relying on details.