How cobalt-strike/external-c2 works
External-C2 specifies a framed protocol linking a third-party controller/client, Cobalt Strike’s External C2 service, and a Beacon session. The repository’s sole source file implements a quick client that connects to the service, requests and runs a stage, opens its named pipe, then relays frames. The README documents broader controller behavior and session tasks; those components are shown as external. The map reflects the sampled client source and documented protocol, not an inspected server implementation.
Main entry points: extc2example.c Client workflow
Components 9
Example client
- Program entry
extc2example.c - Client workflow
extc2example.c - Frame helpers
extc2example.c - Stage execution
extc2example.c
External C2 system
- External C2 service
- Third-party controller
Beacon session
- Beacon named pipe
- Beacon payload
Other components
- Client operator
Connections 10
- Client operator → Program entry: starts client
extc2example.c - Program entry → Client workflow: calls go
extc2example.c - Client workflow → Frame helpers: uses frames
extc2example.c - Client workflow → External C2 service: connects; requests stage
extc2example.c - External C2 service → Client workflow: returns stage and tasks
README.md - Client workflow → Stage execution: runs received stage
extc2example.c - Stage execution → Beacon payload: starts payload
extc2example.c - Beacon payload → Beacon named pipe: serves named pipe
README.md - Client workflow → Beacon named pipe: opens pipe; relays frames
extc2example.c - Third-party controller → External C2 service: connects; exchanges frames
README.md