OpenClaw Security Alert: 500,000 Public Instances, Default Config Exposes Systems

OpenClaw Security Exposure Details
Recent analysis shows significant security risks in publicly accessible OpenClaw installations. According to security researchers, there are currently 500,000 OpenClaw instances on the public internet. Of these, 30,000 have known security risks, and 15,000 are exploitable through known vulnerabilities.
Critical Configuration Issues
The default OpenClaw installation has several security deficiencies:
- Authentication is disabled by default
- The gateway binds to 0.0.0.0, making the system accessible from any network
- No kill switch is included in the system
- No management console is provided
- Data is stored in plain-text markdown files without encryption
This configuration means that if you installed OpenClaw without manually configuring security settings, your entire agent setup is sitting on the open internet for anyone to access.
Documented Security Incidents
Multiple security incidents have been documented:
- A security audit found 341 malicious skills on ClawHub
- 1.5 million API tokens were exposed in a database leak
- One developer found 9 CVEs in their first week of using OpenClaw
- A U.K. CEO's OpenClaw instance was sold on BreachForums for $25,000, giving the buyer access to email, calendar, and files
Immediate Action Required
If you have OpenClaw installed, check your setup immediately:
- Verify authentication is properly configured
- Check your network bindings
- Review your API key security
- Ensure your installation is not publicly accessible without proper security measures
The technology itself is capable, but the default configuration presents significant security liabilities that require immediate attention.
📖 Read the full source: r/openclaw
👀 See Also

Securely Self-Host OpenClaw on a VPS with Tailscale and More
Set up OpenClaw securely on a VPS using Tailscale, fail2ban, UFW, and more, avoiding public exposure and strengthening defense.

Customize Your OpenClaw: Economize and Enhance Security
Discover how to tailor your OpenClaw to not only save money but also to bolster its security, as discussed on the r/openclaw subreddit.

OpenClaw Security Concerns: API Keys and Conversation Data at Risk in Default Self-Hosting
A Cisco report indicates OpenClaw security is "optional, not built in," with default configurations storing API keys in .env files on VPS instances, creating potential exposure for non-technical users running on basic droplets.

PolyRange: Contamination-Resistant Offensive-AI Benchmark with LLM-Generated Targets
PolyRange v1.0 is an MIT-licensed, self-hostable benchmark that generates fresh web targets per run to prevent training data contamination. It includes 84 WSTG-derived classes across all OWASP categories, two defense tiers, and real backends.