Port 5900/tcp: VNC (Virtual Network Computing) / RFB
Category: File Sharing & Remote Access. Range: registered. Status: iana registered.
What runs here
A cross-platform remote-framebuffer protocol (RFC 6143) implemented by numerous independent products (RealVNC, TightVNC, UltraVNC, TigerVNC) rather than being tied to one vendor or OS. Port 5900 corresponds to display :0; additional displays on the same host stack upward (5901 for :1, and so on).
Why it matters
Historically, several VNC implementations have shipped with weak, optional, or outright no authentication, and once a session is established the remote party has the same interactive GUI control as someone sitting at the console: no distinction between a legitimate remote-support session and a full-control backdoor at the protocol level. Internet-exposed, unauthenticated VNC servers are a long-running, low-effort mass-scan target.
Where you see it
Legitimately: remote IT support and screen-sharing tools built on VNC. Anomalously/maliciously: mass scanning for and connecting to unauthenticated internet-exposed VNC servers, or malware bundling a VNC server as a secondary remote-access backdoor.
What to look for
| Signal | What it means |
|---|---|
| VNC server process on an unexpected host | Process creation for a VNC server binary (e.g. winvnc.exe, tvnserver.exe) on a system with no legitimate remote-support justification is worth investigating as a potential backdoor. |
ATT&CK techniques
- T1021.005: T1021.005