Stop Binding 0.0.0.0: Preventing OpenClaw Internet Exposure
Defaulting to 0.0.0.0 exposes your AI agent's control panel to the entire internet. Shodan currently lists 42,000+ exposed instances.
The Mistake: 0.0.0.0 Everywhere
Many community setup guides recommend `0.0.0.0` to simplify mobile and cross-device testing. That advice is operationally convenient, but it collapses your trust boundary when host firewalls or cloud security groups are weak.
OpenClaw admin surfaces were never intended to be directly internet reachable without a hardened access layer. Binding globally is not a harmless default for a tool that can execute actions on your infrastructure.
The Risk: Session Theft and Key Exposure
When the panel is publicly reachable, attackers can probe authentication edges, scrape metadata, and target stored session artifacts. In real incidents we observed theft of Moltbook cookies, provider API keys, and environment variables used by deployment pipelines.
Once a session is hijacked, the attacker can submit automation jobs that appear legitimate to downstream systems.
The Fix: Local Bind + Private Access
Bind the service to `127.0.0.1`, then use a private overlay such as Tailscale or WireGuard for remote operator access. This pattern keeps the control plane off the public internet while preserving remote workflows.
bash
# openclaw service flags
--host 127.0.0.1
--port 3000
# access remotely only via VPN tunnel
# tailscale up --ssh
# wireguard: allow trusted peer IPs only