Port 20/tcp: FTP (File Transfer Protocol): Data
Category: File Sharing & Remote Access. Range: well-known. Status: iana registered.
What runs here
The secondary channel an FTP session uses to move actual file bytes, separate from the command channel on port 21. In active mode the FTP server initiates this connection back to the client's specified port using the PORT command; in passive mode (the default in virtually all modern clients), the server instead opens a random high port and the client connects out to it, so raw port-20 traffic is actually the less common case today.
Why it matters
Because file contents cross this channel in the clear unless the session is wrapped in FTPS, a packet capture of port 20 traffic can hand an analyst the exact bytes an attacker exfiltrated or staged. Its more distinctive DFIR signal is behavioral: a server-initiated inbound connection from port 20 back to a client is what FTP bounce/active-mode abuse and FTP-based port-scanning-through-a-third-party rely on, since it lets an attacker make a target believe scan traffic originated from the FTP server rather than from them.
Where you see it
Legitimately: an FTP client in active mode receiving a file, or a server responding to a PORT command. Anomalously/maliciously: malware using an FTP data channel to exfiltrate collected files or pull down a secondary payload, or an attacker abusing the FTP PORT command (the classic "FTP bounce" technique) to relay scan/connection traffic through the FTP server toward a third host.
What to look for
| Signal | What it means |
|---|---|
| Active vs. passive mode | A genuine inbound connection sourced from tcp/20 only happens in active mode; passive-mode transfers (the modern default) never touch port 20 at all, so real port-20 traffic on the wire is itself worth a second look. |
Related ports
- 21/tcp: FTP (File Transfer Protocol): Control
ATT&CK techniques
- T1071.002: T1071.002