CyberKit

Network ports

Port 6667/tcp: IRC (historical botnet C2 channel)

Category: Malware & C2 (DFIR-Notable). Range: registered. Status: historical documented.

What runs here

6667 is the conventional default port for IRC (Internet Relay Chat) (a legitimate, decades-old chat protocol in its own right) that became, through the 2000s in particular, one of the most common command-and-control channels for botnets. Malware families like Agobot/Phatbot and Kaiten/Tsunami connected outbound to an attacker-run IRC server/channel to receive commands, a pattern SANS Internet Storm Center documented in a dedicated write-up on whether IRC traffic 'is evil,' and which the nmap project still ships a dedicated NSE script (irc-botnet-channels) to help detect.

Why it matters

Unlike the other entries in this category, 6667 is IRC's genuine standard port rather than an arbitrarily chosen one, which means the relevant DFIR judgment call isn't 'is this port suspicious' so much as 'does this environment have any legitimate reason to run IRC at all.' Because modern botnets have largely shifted to HTTP(S)/DNS-based C2 to blend into normal traffic, unexpected outbound 6667 traffic from a workstation or server (as opposed to a dedicated, sanctioned chat client) is a comparatively high-confidence signal worth investigating, even though the technique itself is dated.

Where you see it

Legitimate use: sanctioned IRC clients on hosts where chat is an approved business tool (increasingly rare in modern enterprises). A red flag: outbound 6667 connections from servers, workstations without an approved IRC client, or any host exhibiting other signs of compromise, especially with periodic beacon-like reconnection behavior.

ATT&CK techniques

  • T1071: Application Layer Protocol

Sources