Port 1080/tcp: SOCKS Proxy
Category: Web & Application. Range: registered. Status: iana registered.
What runs here
SOCKS is a generic circuit-level proxy protocol that relays arbitrary TCP (and, in SOCKS5, UDP) connections on behalf of a client without understanding the application protocol being tunneled, unlike an HTTP proxy, which works only for HTTP(S). Port 1080/tcp is IANA's registered default, and the current version, SOCKS5, is defined in RFC 1928, with RFC 1929 covering username/password authentication.
Why it matters
Because SOCKS is protocol-agnostic, a SOCKS proxy on 1080 can carry literally anything: a legitimate privacy or bypass tool, or an attacker's pivot channel for tunneling C2, lateral movement, or further scanning through a compromised host. Post-exploitation frameworks commonly stand up an ad hoc SOCKS proxy on a compromised machine specifically to relay follow-on traffic through it, so an unexpected listener or outbound connection on 1080 warrants immediate attention.
Where you see it
Legitimately: privacy or bypass tooling such as SSH dynamic (-D) port forwarding, or Tor's SOCKS interface; enterprise proxy chaining. Anomalously/maliciously: a SOCKS proxy stood up on a compromised host by a post-exploitation framework to relay attacker traffic through the victim network, or a host reaching out to an external SOCKS proxy to evade egress monitoring.
What to look for
| Signal | What it means |
|---|---|
| SOCKS handshake destination | The SOCKS CONNECT request specifies the true target host and port being relayed; decoding it reveals what is actually being tunneled, since the proxy connection itself gives no application-layer visibility. |
Related ports
ATT&CK techniques
- T1090: Proxy