Port / TCP
8888HTTP alternate / Jupyter
Another common unprivileged HTTP port, and the default for Jupyter Notebook and JupyterLab.
If it is internet-facing: Finding 8888 open to the internet is a finding in its own right — it warrants an explanation, not just a rule.
Exposure
Localhost only
Transport
Cleartext
Risk if public
High
Exposure verdict
Port 8888 should be bound to 127.0.0.1. Nothing outside the host needs to reach it, and binding to 0.0.0.0 is the single change that turns it into an incident.
Traffic crosses the network readable and modifiable. Anything sensitive on this port needs a tunnel, a VPN, or a different protocol.
Registered with IANA on request, but bindable by any unprivileged user. Registration records intent — it does not reserve the port, so collisions between products are common.
Grouped with the other web & proxies ports so a rule written for one can be checked against its neighbours.
What actually goes wrong
2 notes- A Jupyter notebook is arbitrary code execution by design — an exposed one with a weak or disabled token is a shell.
- Keep it on localhost and reach it through an SSH tunnel.
Recommended firewall rule
Deny at the edge and bind to loopback
A firewall rule is the second line here. Fix the bind address in the service configuration so the listener never leaves the host.
ufw
sudo ufw deny 8888/tcpiptables
sudo iptables -A INPUT -p tcp --dport 8888 -j DROPIf you do need it open to everyone
sudo ufw allow 8888/tcpWrite down why. An unexplained allow rule outlives the person who added it, and the next reviewer has no way to tell a deliberate exception from an accident.
Check what is really there
Listening locally
sudo ss -tlpn 'sport = :8888'The bind address is the answer that matters: 127.0.0.1 is local-only, 0.0.0.0 and :: mean every interface.
Listening (macOS)
sudo lsof -nP -iTCP:8888 -sTCP:LISTENmacOS ships lsof rather than ss; this names the owning process and user.
From outside
nmap -sV -Pn -p 8888 <host>A version probe confirms whether HTTP alternate / Jupyter is actually what answers, rather than trusting the number. Only scan hosts you are authorised to test.
Reachability
nc -vz <host> 8888The quick yes/no when you only need to know whether a path exists through the firewall.