40,000 OpenClaw Agents Were Left Open to the Internet. Is Yours One of Them?

Your OpenClaw assistant can read your messages, open files, run commands and browse the web for you. That is the point.
It is also the reason the number below should worry you.
The number: 40,000+
In early 2026, security researchers scanned the internet and found more than 40,000 OpenClaw instances exposed to the public internet. SecurityScorecard counted 40,214, spread across roughly 28,000 IP addresses. More than 12,000 of them were vulnerable to remote code execution. An attacker could have taken over the whole machine.
Most of these owners were not careless. They simply kept the defaults.
How it happened
Early OpenClaw versions bound the gateway to 0.0.0.0:18789, which means every network interface, not just your own computer. Put that on a VPS, or forward a port on your router "just to test the phone", and your assistant is reachable by anyone.
On top of that:
- A one-click remote code execution bug (CVE-2026-25253) could reach even local instances through the browser.
- Researchers flagged hundreds of malicious skills on ClawHub.
OpenClaw has fixed a lot since then. The gateway no longer runs without authentication. But old installs and old habits linger.
The 5-minute checklist
1. Is your gateway reachable from outside?
From a different network (for example your phone on 4G), try to open http://YOUR-PUBLIC-IP:18789. If anything loads, stop and fix it now.
2. Bind to localhost.
The gateway should only listen on 127.0.0.1 unless you have a very specific reason not to.
3. Use a real token or password. Make it long and random, and never reuse it from somewhere else.
4. Never port-forward 18789. For remote access, use a private network such as Tailscale, or a tunnel that has authentication in front of it.
5. Update. Many of the worst bugs are fixed upstream. You only get those fixes if you take them. (Updates failing? Here is the Node.js fix.)
6. Be picky about skills. A skill runs with your assistant's permissions. Only install skills you have read, or that come from authors you trust.
7. Run openclaw doctor.
It catches a surprising number of misconfigurations.
Or don't be the one holding the door
Self-hosting OpenClaw securely is absolutely possible. It is also an ongoing job.
On ClawNest, every assistant runs in its own isolated environment in Sweden. Its gateway is never exposed directly to the internet, and it is updated and backed up for you. You get the assistant, and we take care of keeping it locked.
Sources: SiliconANGLE, Techzine, eSecurity Planet.