Hexworth C2 Training Simulator v1.0 • SIMULATED ENVIRONMENT
Select an agent from the sidebar, then type a command below.
Type help for a full command reference.
Command and Control (C2) is the infrastructure an operator uses to communicate with deployed devices. In offensive security, C2 frameworks (Cobalt Strike, Sliver, Mythic) let red team operators send commands to implants on target machines and receive results back. In defensive security, understanding C2 is how you detect and disrupt adversary operations.
Hexworth C2 is the educational version. Instead of controlling software implants on computers, you control hardware devices you built — ESP32 boards, Raspberry Pis, Arduino projects, USB duckies. The C2 pattern is identical: devices check in, receive commands, execute them, and report results. The difference is the context: your devices, your network, your lab.
Two Modes
SIMSimulation Mode
Simulated agents with pre-programmed responses. No real devices, no network calls. Use this to learn the C2 interface, practice commands, and understand how operators interact with agents.
5 simulated agents (USB implant, Pi backdoor, ESP32 beacon, etc.)
Pre-scripted command responses
No authentication required
Safe to explore — nothing real happens
LIVELive Hardware Mode
Real devices you built in Signal House projects. Devices check in via HTTPS to Firebase Cloud Functions. You send real commands and receive real results. This is a working C2 system.
Review the agent details — hostname, IP, OS, implant type
Type commands in the terminal input at the bottom of the Agent Console tab
Try: help to see available commands for the selected agent
Try: sysinfo, netstat, ps, screenshot
Explore the Network Map tab to see agent topology
Check the Loot Vault for captured data
Review the Activity Log for a timeline of all operations
Using LIVE Mode
Sign in on the main Hexworth site first (admin account required)
Click the LIVE toggle in the topbar
The sidebar shows real devices registered with the C2 backend
Click a device to see its live status, IP, firmware, sensors, and capabilities
Type a command matching the device's capabilities (e.g., wifi-scan for an ESP32)
The command is queued in Firestore — the device picks it up on its next poll
Results appear when the device reports back
Connecting Hardware Projects
Each Signal House hardware project (ESP32, Pi, Arduino) can connect to the C2 backend. When you build a project, the guide includes code to register with the C2 API and check in periodically. The device appears in LIVE mode automatically.
Compatible Projects
SG-33 Rubber DuckySG-68 Rogue APSG-64 BLE ScannerSG-60 LoRa CommsSG-09 Network ProbeSG-43+ Pi Servers
Architecture
Device (ESP32/Pi/Arduino)
|
| HTTPS POST (heartbeat every 30s)
v
Cloud Functions (Firebase)
|
| Read/Write
v
Firestore Database
c2_devices/ — device registry + status
c2_commands/ — command queue + results
c2_logs/ — activity history
^
| onSnapshot (real-time)
|
C2 Dashboard (this page)
|
| Dispatch command (Cloud Function)
v
Device picks up command on next poll
Security & Ethics
Hexworth C2 operates exclusively within your own lab environment. All devices you control are hardware you physically built and own. All communication goes through your Firebase project over HTTPS.
Only control devices you built and own
Never deploy on networks you do not have written authorization to test
The C2 pattern teaches how adversaries operate — use this knowledge for defense
Admin authentication is required for all command dispatch operations
All activity is logged in Firestore with timestamps and operator identity