CyberKit

Network ports

Port 4444/tcp: Metasploit Framework default handler

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

What runs here

4444 is the long-standing conventional default LPORT for Metasploit's exploit/multi/handler and for reverse_tcp-family payloads (including Meterpreter), not a port Metasploit invented or was assigned specifically for this purpose (IANA does register TCP/UDP 4444 to a legacy, largely disused service, krb524, the Kerberos v5-to-v4 ticket translator, unrelated to Metasploit), just the value Metasploit and its documentation have used as the out-of-the-box example for years, to the point that SANS Internet Storm Center's own port reference explicitly labels 4444 as the 'Metasploit default listener.' It is trivially changed with a single LPORT option, and penetration testers and red teams routinely do.

Why it matters

Seeing a host make an outbound connection to 4444, or a host on the network start listening on 4444, is a well-known heuristic for 'possible Metasploit/Meterpreter reverse-shell callback': one of the single most common payload delivery mechanisms in both legitimate penetration tests and real intrusions, since it's the path of least resistance for turning an initial exploit into interactive access. Treat 4444 strictly as a lead: real attackers (and testers) frequently pick a different, less conspicuous LPORT specifically because 4444 is so widely fingerprinted and blocklisted.

Where you see it

Legitimately/expected: virtually never outside an authorized, scoped penetration test or red-team engagement, where the tester should have pre-notified the blue team. A red flag in essentially every other context: any unexpected outbound connection to 4444 from an internal host, or an internal host suddenly listening on 4444, warrants immediate triage as a possible reverse-shell callback.

What to look for

Indicators
SignalWhat it means
Outbound beacon to 4444A host initiating a new outbound TCP connection to port 4444 on an external or unfamiliar IP, especially shortly after suspicious process activity, matches the classic Meterpreter reverse_tcp callback pattern.
Process spawned by the connecting parentCorrelating the process that opened the 4444 connection (e.g. a script interpreter or an exploited service process) against expected baseline behavior helps confirm whether this is a legitimate test or unauthorized access.

ATT&CK techniques

Sources