Hackers Exploit OpenClaw Skills to Deliver Malware
A campaign known as ClawHavoc used poisoned packages in OpenClaw's ClawHub skill registry to deliver data-stealing malware, according to Cyber Security News coverage indexed by IT Security News on August 20. The report illustrates how third-party skills for agents with file, messaging, and terminal access can become a software supply-chain delivery path. Earlier research from VirusTotal and Unit 42 documented malicious OpenClaw skills, including infostealers and evasive packages.
A campaign known as ClawHavoc used poisoned packages in OpenClaw's ClawHub skill registry to place data-stealing malware on victim devices, according to Cyber Security News coverage indexed by IT Security News on August 20. The report describes OpenClaw as an open-source agent platform that can interact with local files, messaging applications, and terminal commands, making a malicious extension materially more consequential than an ordinary untrusted script.
The current report follows a series of earlier security findings around the OpenClaw skill ecosystem. In February, VirusTotal reported detecting hundreds of actively malicious OpenClaw skills, including droppers, backdoors, infostealers, and remote-access tools presented as useful automation. VirusTotal described skills as packages centered on a SKILL.md instruction file that can also include scripts and other resources, with users commonly discovering them through the public ClawHub marketplace.
A supply-chain risk shaped by agent permissions
OpenClaw runs locally and can execute shell commands, perform file operations, and make network requests, according to VirusTotal. That combination changes the practical risk model: a marketplace package can use both executable code and natural-language setup instructions to guide a user or agent toward downloading binaries, exporting environment variables, or running terminal commands.
Permiso's February research likewise reported finding a credential stealer disguised as a weather application while testing an OpenClaw agent with access to email, Slack, SharePoint, and calendar services. Its researchers characterized the concern as an emerging attack surface created when autonomous agents hold credentials across multiple business systems.
For security teams, this is an extension of familiar package-registry risk rather than a wholly separate category of malware. The notable difference is that an agent skill can combine dependency code, instructions interpreted by a model, and access to local tools. Comparable agentic systems often expand the impact of a compromised package because the package may operate near credentials, browser sessions, developer tooling, and messaging workflows.
Screening has not eliminated malicious skills
Unit 42 reported in June that early February findings prompted ClawHub to integrate VirusTotal and ClawScan for proactive skill screening and code-level analysis. However, its February-May investigation identified five malicious skills that remained unblocked. Unit 42 said it reported those packages to ClawHub, after which OpenClaw banned the associated accounts and deleted the skills.
The five samples fell into three categories in Unit 42's analysis:
- •Two delivered macOS infostealers and communicated with command-and-control infrastructure.
- •One used an inflated file size intended to exceed scanner thresholds and evade ClawScan and VirusTotal detection.
- •Two used agentic techniques for affiliate injection and front-running intended for financial gain.
The ClawHavoc reporting therefore arrives against a documented pattern of malicious extensions and detection bypass attempts, not as an isolated warning. Unit 42 also reported that OpenClaw had begun requiring documentation of a skill's behavior and planned to run NVIDIA's analysis tool across skills.
Teams deploying self-hosted agents should treat skill installation as a privileged software-supply-chain event. Common controls in comparable environments include reviewing package source and code, limiting filesystem and network permissions, isolating agent runtimes, avoiding broadly available secrets, and monitoring outbound connections and process execution. Those controls do not establish whether any particular ClawHavoc victim was compromised, but they reduce the blast radius when a third-party extension proves malicious.
Key Points
- 1ClawHavoc reportedly used poisoned ClawHub skills for data theft, turning agent extension installation into a malware-delivery route.
- 2VirusTotal and Unit 42 documented earlier malicious OpenClaw skills, showing that marketplace screening alone has faced evasive packages.
- 3Agent ecosystems with local execution and credentials follow supply-chain risk patterns, but broad tool permissions can amplify compromise impact.
Scoring Rationale
The report concerns a practical malware-delivery path in an AI agent ecosystem with local-system and credential access. It is especially relevant to teams deploying self-hosted agents or allowing marketplace extensions, although the available current-event reporting does not establish the campaign's scale or victim count.
Sources
Primary source and supporting public references used for this report.
Practice with real FinTech & Trading data
90 SQL & Python problems · 15 industry datasets
250 free problems · No credit card
See all FinTech & Trading problems

