3 ‐ Client
The client is composed of 3 main sections:
- Listeners section where are listed the Listeners running on the TeamServer and the one running on Beacons.
- Sessions section where are listed the Beacon that connected to a Listener
- Console section with a Terminal tab to interact with the TeamServer and Sessions tab to interact with active Beacons.
Terminal tab is use to interact with the TeamServer. You can type ,"help" to get the list of available command. They are implemented using GRPC command and python modules making the integration of new technique quick and easy.
New droppers can be added creating new git repo to the "DropperModules.conf" file, they need to meet some light requirement and are then available using the Dropper command:
Socks5 server is now also part of the Terminal panel, "Socks start" start a socks server on port 1080 then the bind command, link the socks5 server to the running beacon:
The setup of the socks proxy is done like this:
Then we force a low sleep timer on the beacon, it is because the socks traffic will go through the HTTP link that is connecting the beacon and the server:
Right click - Interact:
Then we can use the socks with proxychains:
Session tab is use to interact with a Beacon, send command and display responses:
At the start of the Client, python scripts located in the Script folder are loaded. Different triggers are already implemented to enable scripting of the client, see: https://github.com/maxDcb/C2TeamServer/blob/master/C2Client/C2Client/Scripts/