Port 143/tcp: IMAP (Internet Message Access Protocol)
Category: Email. Range: well-known. Status: iana registered.
What runs here
IMAP synchronizes a mail client's view of a mailbox with a server-resident copy, supporting multiple folders and flags with simultaneous access from multiple devices, unlike POP3's simple download model. Port 143/tcp is its IANA-registered default; the current protocol version is IMAP4rev2, defined in RFC 9051, which supersedes the long-standing IMAP4rev1 in RFC 3501. Like POP3, plaintext IMAP negotiates STARTTLS to upgrade to encryption, or can be used entirely unencrypted if the client allows it.
Why it matters
Because IMAP is the most feature-rich mailbox-access protocol, it is a particularly attractive target for credential-based mailbox abuse: an attacker with valid credentials can browse folder structure, search, and selectively exfiltrate specific mail rather than bulk-downloading everything, which is harder to distinguish from normal usage than a POP3 bulk retrieval. IMAP access is also frequently how post-compromise mailbox persistence plays out in practice. Attackers using OAuth-token abuse (XOAUTH2) to maintain IMAP access, often alongside forwarding rules configured through the mail platform's own webmail or admin API rather than IMAP itself, to keep visibility into a victim's mail after the original access vector is remediated.
Where you see it
Legitimately: standard mail client access on desktop and mobile to a server-resident mailbox, multi-device synchronization. Anomalously/maliciously: credential-stuffing or brute-force against IMAP, or an attacker with compromised credentials or OAuth tokens using IMAP to search and selectively exfiltrate mail, for example searching for invoice or wire-transfer related terms as part of BEC reconnaissance, while leaving most of the mailbox untouched.
What to look for
| Signal | What it means |
|---|---|
| SEARCH/FETCH command patterns | Targeted SEARCH queries for financial or credential-related keywords followed by selective FETCH of specific messages is a common BEC and mailbox-reconnaissance pattern, distinct from a normal client's bulk sync behavior. |
| Login source IP/ASN vs. account's normal pattern | A successful IMAP login from an unfamiliar country or ASN immediately after a phishing click is a strong compromised-account indicator. |