External Tor Hidden Service bridge for Sliver C2 (avoiding core modifications)

[Otsmane-Ahmed]

Hi all,

I've been working on a way to easily route Sliver C2 traffic through Tor Hidden Services without needing to modify the core Sliver Go codebase or deal with complex manual Tor configurations.

I built an external Python bridge that automates this process:
https://github.com/Otsmane-Ahmed/sliver-tor-bridge

How it works:

1. It sits in front of your Sliver server (like a sidecar).
2. Automatically generates a Tor Hidden Service .onion address.
3. Proxies incoming traffic from Tor to your local Sliver HTTPS listener.

This allows for fully anonymous C2 infrastructure where the server's real IP is never exposed to the implant, and because it works as an external proxy, it's compatible with any version of Sliver.

I've already submitted it to the Armory (Issue #XX), but wanted to open a discussion here to get feedback on this "external bridge" approach versus native integration.

Is this something commonly needed? Any security concerns I might have missed in the implementation?

Feedback welcome!