Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Sliver is an open-source command-and-control framework written in Go, used by red teams for implant generation, multi-protocol communication, and collaborative operations.

What Is Sliver?
Sliver is a command-and-control framework: the server-side infrastructure, implants, and operator console that a red team uses to control compromised hosts during an engagement. Bishop Fox released it as open source in 2019, written in Go, and it has since become the most widely used free alternative to commercial tooling.
The appeal is partly technical and partly economic. Go cross-compiles to Windows, Linux, and macOS from one codebase, so a single framework covers mixed estates. And because it is free, it is available to everyone, which is precisely why defenders need to know it.
A Sliver deployment has three moving parts. The server holds operator accounts, generated implants, listeners, and the database of active sessions. Implants run on target machines and connect back. The client is the operator console, which can run on the server or connect remotely, allowing several operators to share one engagement with separate credentials and an audit trail.
Implants come in two flavours. Session implants hold an interactive connection; beacon implants check in on an interval with jitter, trading responsiveness for stealth. The transport is chosen per listener:
| Transport | Characteristics |
|---|---|
| mTLS | Mutually authenticated TLS with per-implant certificates; fast and encrypted |
| WireGuard | Virtual network interface to the implant, allowing tooling to reach the host directly |
| HTTP and HTTPS | Blends with web traffic and works through proxies |
| DNS | Slow but survives environments where only resolution is permitted |
Sliver compiles a fresh implant for each build, with per-binary encryption keys and certificates, so file hashes do not repeat between engagements or between victims. That alone breaks naive detection. The framework also supports staged and stageless payloads, shellcode output, and an extension system called the armoury that adds third-party capabilities, including execution of Beacon Object Files originally written for other tooling.
The practical consequence for a defender is that catching Sliver by file hash is not a strategy. Detection has to rest on behaviour and on network characteristics that survive recompilation.
Both sides. Legitimate red teams adopted it quickly because it is capable, free, and does not require a licence per operator. Criminal and state-aligned groups adopted it for the same reasons, plus one more: using a tool that thousands of penetration testers also use muddies attribution. Microsoft published research in 2022 describing Sliver’s adoption by ransomware affiliates and nation-state actors as a replacement for commercial frameworks whose cracked versions had become heavily signatured.
That dual use is the normal condition of this tool class, shared with PowerShell Empire and the Meterpreter payload in Metasploit. Finding any of them on a host is an incident until the security team can prove otherwise.
Network analysis gives the most durable signals. Beaconing produces a connection pattern with a recognisable rhythm, and even with jitter the statistical regularity stands out over hours in Zeek or proxy logs. TLS fingerprinting is effective: JA3 and JA3S hashes derived from Go’s TLS stack differ from the browsers and agents on your estate, and default mTLS listeners present certificates with characteristic attributes. DNS transport is the loudest of all, producing long encoded labels and query volumes no ordinary client generates.
On the host, watch for unsigned binaries making regular outbound connections, Go runtime artefacts in memory, named pipe creation for in-process communication, process injection into otherwise idle processes, and the usual post-exploitation behaviours that follow once a session is live: credential access, directory enumeration, and lateral movement attempts.
Default-deny egress through an inspecting proxy removes the easy transports and forces an operator onto DNS, which is far easier to spot. Internal DNS policy that permits resolution only through your own resolvers, with logging and anomaly detection on query length and volume, closes the fallback. Application control stops unsigned binaries from executing in user-writable paths, which blocks the most common delivery route. Endpoint detection with behavioural rules catches injection and credential access regardless of which framework is in use.
At Privia Security, our Red Team Services use frameworks of this class under agreed rules of engagement, which is the most direct way to find out whether these detections work in your environment rather than in a vendor datasheet.
The framework is lawful, open-source software published for security testing. Deploying an implant on a system you do not own or have written permission to test is unauthorised access and an offence under the Computer Misuse Act 1990 in the UK. Authorised engagements operate under signed rules of engagement that name the systems and the testing window.
Cobalt Strike is commercial software with a mature operator workflow, malleable traffic profiles, and extensive tooling built around it. Sliver is free and open source, written in Go rather than Java and C, and cross-compiles natively for several platforms. Detection approaches overlap heavily, since both rely on beaconing implants and in-memory execution.
Default builds are detected by most modern products, but Sliver generates a unique binary with fresh keys for each implant, so hash-based detection fails on anything customised. Reliable detection comes from behaviour on the endpoint, such as injection and credential access, combined with network analysis of beaconing patterns and TLS fingerprints.
Cost is one reason, since there is no licence to buy or crack. Attribution is another: when thousands of legitimate testers use the same tool, its presence tells an investigator very little about who is behind an intrusion. Open source also lets operators modify the code to evade detections written against the stock release.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.