HackTheCore
ResearchInternal OperationsPivoting & Portforwarding

Network // Internal Operations

Pivoting & Portforwarding

This Internal Operations field brief frames Pivoting & Portforwarding around the trust boundaries an authorized assessor needs to verify. Use it to plan safe validation, capture reproducible evidence and distinguish a meaningful control failure from an isolated technical symptom.

field noteassessment referencepublic sources

Why it matters in practice

Within Internal Operations, Pivoting & Portforwarding changes how scope, prerequisites and evidence should be handled. Focus on the concrete asset or data flow under test, record the assumptions that make the condition exploitable and connect verified behavior to an operational consequence and remediation decision.

This note keeps Pivoting & Portforwarding tied to offensive workflow: what to observe, what to prove, what usually goes wrong, and which references remain useful once an assessment moves from planning into active validation.

Primary coverage

The coverage below turns Pivoting & Portforwarding into an assessment map for Internal Operations: identify the relevant system boundary, select a safe validation path, preserve evidence and record uncertainty before drawing a conclusion.

  • Pivoting
  • Pivoting via SSH and socks proxy
  • Building an SSH tunnel
  • Adjusting proxychains in kali
  • Sending commands through proxychains
  • Pivoting via metasploits meterpreter
  • Listing active meterpreter sessions
  • Pivoting via meterpreter
  • Pivoting via netcat
  • Ncat http proxy

Assessment focus

ssh -D localhost:9000 -f -N daniel@10.1.2.3
socks5 127.0.0.1 9000
proxychains nmap -sV 10.2.3.4
msf6 auxiliary(scanner/ftp/anonymous) >  route add 10.1.2.0/24 1
[*] Route added
msf6 auxiliary(scanner/ftp/anonymous) > use auxiliary/server/socks4a
msf6 auxiliary(server/socks4a) > set SRVPORT 9050
SRVPORT => 9050
msf6 auxiliary(server/socks4a) > run -j
[*] Auxiliary module running as background job 2.

[*] Starting the socks4a proxy server
msf6 auxiliary(server/socks4a) >
ncat -vv --listen 1337 --proxy-type http
socat tcp-l:5050,fork,reuseaddr tcp:127.0.0.1:1337

# Port 5050 = Listenport
# Port 1337 = Port that receives the forwarded traffic.
./redir :1234 10.1.2.3:5678
beacon> socks 3333

Selected public references

Related research

Compare the adjacent Internal Operations briefs below to test whether the same assumption, evidence pattern or mitigation boundary appears elsewhere in the domain.