Skip to content

Sliver C2

Tony West edited this page Aug 10, 2026 · 2 revisions

Sliver C2

The Execute tab can connect to a Sliver teamserver as an alternative to deployed web shells. Once connected, you can drive active sessions and beacons directly from the Joro UI.

Mythic-C2 is the other supported C2 integration.

Generating an operator config

On your Sliver teamserver, generate an operator configuration for yourself:

new-player --operator <your-nickname> --lhost <teamserver-ip> --save /tmp/<your-nickname>.cfg

This produces a JSON configuration that contains the teamserver address, port, and mTLS credentials needed to authenticate.

Connecting

In the Joro UI, open the Execute tab and switch to Sliver mode. Paste the operator config JSON directly, or upload the .cfg file. Joro will connect to the teamserver and list the active sessions and beacons.

Select the session or beacon you want to drive. From that point on, commands typed into the terminal are dispatched through Sliver's RPC layer.

What you can do

From the Joro terminal you can run the same sliver-client commands you would in the standalone client, including:

  • Execute OS commands on the target.
  • Download files (cached briefly server-side for you to fetch).
  • Take screenshots.
  • Dump processes.
  • Upload files to the target.

Output streams back into the terminal pane. Binary results such as screenshots and procdumps are made available for download.

Disconnecting

Click disconnect to drop the gRPC connection to the teamserver. Sessions and beacons are not affected; you can reconnect and resume at any time.

Clone this wiki locally