Port 9001/tcp: Tor ORPort (relay traffic)
Category: Malware & C2 (DFIR-Notable). Range: registered. Status: historical documented.
What runs here
9001 is the port the Tor Project's own sample relay configuration (torrc.sample.in) and relay-setup documentation use for the ORPort: the port a Tor relay listens on to carry onion-routed traffic between other relays in the network. It's a documented convention rather than a hardcoded requirement; a relay operator can bind ORPort to any port (443 is also commonly recommended precisely because it blends in on restrictive networks), so 9001 specifically is a strong lead, not a guarantee, when triaging Tor-related traffic.
Why it matters
Tor is legitimate anonymity software, but it's also a well-documented technique adversaries use to route C2 traffic through a multi-hop encrypted network that's very difficult to trace back to its source (MITRE ATT&CK's own Multi-hop Proxy technique names Tor explicitly). Seeing a host establish connections consistent with Tor relay/client traffic on an internal server with no legitimate reason to run Tor is worth flagging, both as possible C2 channeling and as a policy violation in most enterprise environments.
Where you see it
Legitimate use: an intentionally operated Tor relay/bridge (rare and normally an explicit, known decision in an enterprise) or a user running the Tor Browser for legitimate privacy reasons per policy. Anomalously/maliciously: a server or unexpected workstation exhibiting Tor-consistent connection patterns with no sanctioned business reason, particularly alongside other signs of compromise.
Related ports
- 9030/tcp: Tor DirPort (directory service)
ATT&CK techniques
- T1090.003: T1090.003