1,184 malicious skills on ClawHub. That's what security researchers found lurking on OpenClaw's official skill marketplace. The supply chain attack, dubbed ClawHavoc, didn't just sit there. It actively stole SSH keys, API tokens, crypto wallets, and browser credentials from anyone who installed the wrong package.
What the Malicious ClawHub Skills Actually Did
A Snyk ToxicSkills study found that 36.82% of all ClawHub skills had security flaws. 13.4% were critical. But ClawHavoc was something else entirely. This was coordinated.
335 of those clawhub malicious skills traced back to a single campaign using Atomic Stealer malware. All 335 phoned home to one command-and-control server at 91.92.242.30. The primary attacker account, "hightower6eu," uploaded somewhere between 314 and 677 malicious packages, depending on which security firm you ask. Twelve publisher accounts were linked to the operation in total.
The malicious ClawHub skills looked legitimate. They mimicked popular tools, used similar names, even copied descriptions. Once installed, they quietly exfiltrated credentials and sent them upstream.
How OpenClaw and Governments Responded
ClawHub's response included a VirusTotal partnership for automated scanning, an auto-hide mechanism after three community reports, and a newly hired security advisor. Whether that's enough is debatable.
Governments moved too. Belgium's CCB issued warnings. China's MIIT flagged the risk. South Korea restricted access to certain ClawHub features.
Andrej Karpathy called the marketplace "a dumpster fire." Gartner classified OpenClaw as "insecure by default." Not exactly a vote of confidence.
What This Means If You Run OpenClaw
If you self-host, you need to vet every single skill before installing it. Check the publisher, check the source code, check the download count. It's tedious. Most people skip it.
On ClawHosters, instances run the built-in safety scanner (shipped in v2026.2.6) by default. Skill installation goes through a curated process, not blind downloads from the marketplace. That's the core argument for managed hosting over DIY. You don't have to be the security team.
The full technical breakdown is in our OpenClaw security hardening guide.