Individual skill

performing-network-pivoting-and-tunneling

Pivoting through compromised hosts and tunneling traffic to reach segmented internal networks using SSH local/remote/dynamic forwarding, chisel, ligolo-ng, socat, sshuttle, proxychains, and SOCKS proxies during authorized engagements.

internal/tools/skills/data/penetration-testing/performing-network-pivoting-and-tunneling/SKILL.md

Read pinned source

Source commit d42f381ad34843e71a42658e5c57290c713e85af

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,313
Repository last updated
Nov 7, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Performing Network Pivoting and Tunneling

## When to Use

- After compromising a dual-homed host that can reach an internal network you cannot
- When a target service is only reachable from a jump/pivot host (DMZ -> internal segregation)
- When you need to run local tools (nmap, smbclient, evil-winrm, RDP) against hosts behind a pivot
- When an egress firewall only permits outbound HTTPS and you must tunnel C2/return traffic
- When relaying reverse shells out of an internal host through a chain of compromised boxes

## Critical: Techniques Most Often Missed

The classic mistake is forgetting that SOCKS/proxychains cannot carry ICMP or SYN scans, then concluding "the host is down". Always scan correctly through a proxy.