Security Alert
135,000+ OpenClaw instances are publicly accessible without authentication. The ClawHavoc supply chain attack (Feb 2026) compromised hundreds of self-hosted setups. Here's what you need to know.
Self-hosted instances reachable without authentication (Cisco Talos, 2026)
Malicious skills placed on ClawHub in the ClawHavoc campaign (Feb 2026)
MyOpenClaw instances affected — all skills are version-pinned + hash-verified
These aren't theoretical. All three have been exploited in the wild.
Out of the box, OpenClaw binds its HTTP gateway to 0.0.0.0 (all interfaces) with no authentication. Anyone who can reach your IP and port can send messages to your AI, access your memory, and invoke your integrations. 135,000+ instances on the public internet are reachable this way.
Cisco Talos published warnings about exposed OpenClaw instances being used as open proxies. Search engines like Shodan index thousands of them daily.
In February 2026, the ClawHavoc campaign placed 341 malicious skills on ClawHub — the community skill registry. These skills executed arbitrary code on installation. Self-hosted users running `clawhub install` without version pinning were silently compromised.
The attack exploited the fact that `clawhub install @latest` trusts whatever the registry serves. Hardcoded @latest references are the attack surface.
OpenClaw ships frequent updates, often with breaking config changes. Many self-hosters fall behind — running versions months out of date, missing security patches. Staying current requires reading changelogs, testing compatibility, and manually updating on your schedule.
Version fragmentation also makes community support harder. The most common self-hosting issues are already fixed in the current release.
Every protection below is active on every instance, by default.
Every MyOpenClaw instance is protected by a unique HMAC-SHA256 gateway token. No token, no access — your AI is not reachable from the public internet without it.
We don't use @latest. Every skill installed on MyOpenClaw instances is pinned to an exact version with SHA-256 hash verification. ClawHavoc-style attacks cannot substitute a malicious package.
We track every OpenClaw release. Security patches are tested and deployed automatically. Your instance stays current without you touching a terminal.
Setup passwords, gateway tokens, and API keys are encrypted with AES-256-GCM before storage. Key rotation is supported without re-encrypting existing records.
All integrations go through a manual verification process before we ship them. Only official CLIs and verified ClawHub registry entries are included — community forks excluded regardless of quality.
Your instance runs on its own Fly.io machine, isolated from other users. Network policies prevent cross-tenant traffic. No shared compute, no shared storage.
If you run self-hosted OpenClaw, verify these three things now:
Skip the configuration gauntlet. MyOpenClaw deploys OpenClaw with authentication enabled, supply chain protections active, and automatic security updates — before you've finished your coffee.
Start Secure HostingStarts at $29/mo. Cancel anytime. No contracts.
