Port 69/udp: TFTP (Trivial File Transfer Protocol)
Category: Network Infrastructure. Range: well-known. Status: iana registered.
What runs here
A minimal, connectionless file-transfer protocol with no authentication and no directory listing: a client sends a read or write request and the server streams the file in fixed-size blocks. It's the standard mechanism for PXE network-boot images and for backing up/restoring configuration on network devices (routers, switches, VoIP phones).
Why it matters
Because TFTP has no authentication, anything reachable over it is available to anyone who can reach the port, and it's the textbook transport adversaries use to pull a compromised network device's running configuration (which can contain hashed or plaintext credentials, SNMP community strings, and routing details) off to attacker-controlled infrastructure. Seeing TFTP traffic to or from a router/switch outside a planned maintenance window is a strong signal of device-level compromise, not routine administration.
Where you see it
Legitimately: scheduled configuration backups, firmware upgrades, and PXE boot of diskless/imaging clients (often handed a TFTP server address via DHCP options 66/67). Anomalously/maliciously: a network device pushing its running-config to an unfamiliar external IP over TFTP, or unsolicited TFTP read requests probing for exposed files.
What to look for
| Signal | What it means |
|---|---|
| Config file transfer to external host | A TFTP write/read of a file named like a device config (e.g. 'running-config', 'startup-config') to or from an IP outside the management network is the core signature of the config-exfiltration technique documented in real router-compromise campaigns. |
| DHCP option 66/67 tie-in | Cross-referencing which TFTP server address a host received via DHCP (option 66 server name / 67 boot filename) confirms whether a given TFTP session was part of an expected PXE boot flow. |
Related ports
- 67/udp: DHCP Server (BOOTPS)
ATT&CK techniques
- T1602.002: T1602.002