Port 1337/tcp: "Leet" port (generic backdoor/CTF culture)
Category: Malware & C2 (DFIR-Notable). Range: registered. Status: historical documented.
What runs here
1337 (leetspeak for 'elite,' the same wordplay behind 31337) is IANA-registered for an unrelated legitimate service (menandmice-dns, the Men & Mice DNS Server Controller protocol) and has no single dominant malware family, but it does have a genuine documented history: SANS Internet Storm Center's own port reference lists both that legitimate menandmice-dns registration and the historical Shadyshell trojan against TCP 1337 (with the original Shadyshell source archived on Packet Storm), and the number's hacker-culture cachet has made it a recurring, informal choice for CTF challenges, bind-shell exercises, and various ad hoc backdoors ever since.
Why it matters
Unlike 31337 or 12345, 1337 isn't tied to one well-documented historical trojan family. Its DFIR value is almost entirely about the port number's cultural significance making it a disproportionately popular arbitrary choice for exactly the kind of informal, hand-rolled bind/reverse shell an attacker (or a penetration tester) sets up on the fly. Treat any listener or connection on 1337 as exactly what this whole category is about: a pivot point worth investigating, never a confirmed finding on its own. Legitimate menandmice-dns and CTF/training infrastructure also use this port, so context matters enormously.
Where you see it
Legitimate use: the registered menandmice-dns service, CTF competition infrastructure, security training labs, and some developer tools/games that lean into the 'leet' naming for fun. A red flag in a production environment with no menandmice deployment: any unexpected listener or outbound connection on 1337 warrants the same triage as any other unfamiliar open port or callback.
Related ports
- 31337/udp: Back Orifice (historical)
ATT&CK techniques
- T1571: Non-Standard Port