# Sliver

## Sliver

<https://github.com/BishopFox/sliver>

[sliver](https://gitlab.com/johnmkane/tech-recipe-book/-/blob/main/Book/Pentest/Red%20Team/C2%20Frameworks/Sliver/Sliver/sliver/README.md)

## [Sliver](https://github.com/BishopFox/sliver#sliver)

Sliver is an open source cross-platform adversary emulation/red team framework, it can be used by organizations of all sizes to perform security testing. Sliver's implants support C2 over Mutual TLS (mTLS), WireGuard, HTTP(S), and DNS and are dynamically compiled with per-binary asymmetric encryption keys.

The server and client support MacOS, Windows, and Linux. Implants are supported on MacOS, Windows, and Linux (and possibly every Golang compiler target but we've not tested them all).

## [v1.6.0 / `master`](https://github.com/BishopFox/sliver#v160--master)

**NOTE:** You are looking the latest master branch of Sliver v1.6.0; PRs should target this branch starting on 6/1/2023 ('MURICA format). However, this branch is NOT RECOMMENDED for production use yet. Please use release tagged versions for the best experience.

For PRs containing bug fixes specific to Sliver v1.5, please target the `[v1.5.x/master` branch]\(<https://github.com/BishopFox/sliver/tree/v1.5.x/master>).

#### [Features](https://github.com/BishopFox/sliver#features)

* Dynamic code generation
* Compile-time obfuscation
* Multiplayer-mode
* Staged and Stageless payloads
* [Procedurally generated C2](https://github.com/BishopFox/sliver/wiki/HTTP\(S\)-C2#under-the-hood) over HTTP(S)
* [DNS canary](https://github.com/BishopFox/sliver/wiki/DNS-C2#dns-canaries) blue team detection
* [Secure C2](https://github.com/BishopFox/sliver/wiki/Transport-Encryption) over mTLS, WireGuard, HTTP(S), and DNS
* Fully scriptable using [JavaScript/TypeScript](https://github.com/moloch--/sliver-script) or [Python](https://github.com/moloch--/sliver-py)
* Windows process migration, process injection, user token manipulation, etc.
* Let's Encrypt integration
* In-memory .NET assembly execution
* COFF/BOF in-memory loader
* TCP and named pipe pivots
* Much more!

#### [Getting Started](https://github.com/BishopFox/sliver#getting-started)

Download the latest [release](https://github.com/BishopFox/sliver/releases) and see the Sliver [wiki](https://github.com/BishopFox/sliver/wiki/Getting-Started) for a quick tutorial on basic setup and usage. To get the very latest and greatest compile from source.

#### [Linux One Liner](https://github.com/BishopFox/sliver#linux-one-liner)

`curl https://sliver.sh/install|sudo bash` and then run `sliver`

#### [Help!](https://github.com/BishopFox/sliver#help)

Please checkout the [wiki](https://github.com/BishopFox/sliver/wiki), or start a [GitHub discussion](https://github.com/BishopFox/sliver/discussions). We also tend to hang out in the #golang Slack channel on the [Bloodhound Gang](https://bloodhoundgang.herokuapp.com/) server.

#### [Compile From Source](https://github.com/BishopFox/sliver#compile-from-source)

See the [wiki](https://github.com/BishopFox/sliver/wiki/Compile-From-Source).

#### [Feedback](https://github.com/BishopFox/sliver#feedback)

Please take a moment and fill out [our survey](https://forms.gle/SwVsHFNh24ChG58C6)

#### [License - GPLv3](https://github.com/BishopFox/sliver#license---gplv3)

Sliver is licensed under [GPLv3](https://www.gnu.org/licenses/gpl-3.0.en.html), some sub-components may have separate licenses. See their respective subdirectories in this project for details.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://book.konstantinsecurity.com/readme/pentest/red-team/c2-frameworks/sliver.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.