"Is my security camera hackable?" is a reasonable thing to wonder — IP camera footage ending up indexed on camera-search sites is a real and well-documented problem, and it almost always comes down to the same two mistakes: a default password that was never changed, and a streaming port left open to more of the network (or internet) than it needed to be. Here's how to check your own setup in a few minutes.
The two things that actually expose a camera
Camera exposure incidents almost never involve a sophisticated exploit. They come down to:
- Default or weak admin credentials — most cheap IP cameras ship with
admin/admin,admin/12345, or a password printed on the box that's identical across the entire product line. - Port forwarding turned on carelessly — some camera apps ask you to enable UPnP or manually forward a port "for remote viewing" without explaining that this makes the camera reachable from the open internet, not just your phone.
Step 1 — Find the camera on your network
Run a device discovery scan and look for the manufacturer name attached to each result — camera brands (Hikvision, Dahua, Reolink, Wyze, TP-Link/Tapo, and generic ODM chipsets) usually resolve clearly through MAC OUI lookup. If you're not sure which device is which, see our guide on finding every device on your WiFi.
Step 2 — Check what ports it has open
Once you've identified the camera's IP address, run a port scan against it specifically. The ports that matter most for cameras:
- 554 (RTSP) — the actual video stream. Should be reachable from your phone/NVR on the LAN, never from outside it.
- 80 / 8080 (HTTP admin) — the web-based configuration panel. If this is reachable from outside your network, anyone who finds the IP can attempt to log in.
- 23 (Telnet) — a disturbing number of budget cameras leave this open with a hardcoded or undocumented credential. There is essentially no legitimate reason for this to be open.
Port open on your LAN scan is normal — the real question is whether it's also open from the internet. Log into your router's admin panel and check the "Port Forwarding" or "Virtual Server" section. If you see an entry pointing to your camera's IP that you don't remember creating, remove it.
Step 3 — Change the password, even if you "already did"
Some camera firmware resets the admin password on factory reset or firmware update without warning. If it's been more than a few months, log in directly and verify the password is still what you think it is — don't assume.
Step 4 — Prefer cloud-free, local-only setups where possible
Cameras that require a manufacturer cloud account to view footage remotely typically achieve that by having the camera phone home to the vendor's servers constantly — which is a different (and harder to audit) risk surface than a camera you access directly over your own network. If remote viewing matters to you, look for VPN-based remote access to your own router instead of vendor cloud relay.
Make it a recurring check
Firmware updates, factory resets, and even router replacements can silently re-expose a camera that was previously locked down. Treat a camera network audit the same way you'd treat checking smoke detector batteries — a five-minute check every few months, not a one-time setup step. ProbeShield's scan history makes it easy to compare today's open-port list on a camera against the last time you checked, entirely on-device.