Vulnerability high
Severity
high
no CVSS

ToxicSkills: 36 Percent of Audited Agent Skills Carried Security Flaws, and 8 Malicious Ones Were Still Live

ToxicSkills: 36 Percent of Audited Agent Skills Carried Security Flaws, and 8 Malicious Ones Were Still Live is a high-severity prompt injection issue in 36 Percent of Audited Agent Skills Carried Security, an agent skill. Affected: 3,984 skills audited across ClawHub and skills.sh: 1,467 flawed, 534 critical, 76 confirmed malicious payloads.

Is 36 Percent of Audited Agent Skills Carried Security running on your developers' machines? Anomity finds every device with this agent skill installed, shows the version, and can block it by policy. Detect this across your developers' devices with Anomity →

Key facts

ID
toxicskills-36-percent-of-audited-agent-skills-carried-security-flaws
Severity
high
Attack type
Prompt injection, Supply chain compromise
Component
36 Percent of Audited Agent Skills Carried Security · agent skill
Known exploited
No known exploitation
Published
Last verified

What is this vulnerability?

Snyk audited 3,984 agent skills across the ClawHub and skills.sh marketplaces and found 1,467 of them, 36 percent, carrying security flaws, 534 of those rated critical. Seventy-six confirmed malicious payloads were identified, and 91 percent of the malicious skills used prompt injection to do their work. Eight were still live on ClawHub when the research published, affecting OpenClaw, Claude Code and Cursor users. The number that matters for governance is the base rate: this is not a handful of bad uploads to take down, it is a marketplace where roughly a third of the catalogue fails review.

Affected versions

AffectedFixed in
3,984 skills audited across ClawHub and skills.sh: 1,467 flawed, 534 critical, 76 confirmed malicious payloadsNo fixed version listed

Am I affected by this vulnerability?

You are affected if you run 3,984 skills audited across ClawHub and skills.sh: 1,467 flawed, 534 critical, 76 confirmed malicious payloads.

How do I fix it?

Audit the skills already sitting on developer machines rather than only gating new installs, and rotate API keys and cloud credentials any installed skill could reach. Check agent memory files for unauthorized edits too, since a malicious skill that already ran may have left instructions behind. At a one-in-three flaw rate an allowlist of reviewed skills is the workable control; a blocklist of known-bad ones is not.

How do I find every machine running 36 Percent of Audited Agent Skills Carried Security?

Anomity inventories the AI agents, MCP servers, IDE extensions and skills on each developer device, so you can see which machines run 36 Percent of Audited Agent Skills Carried Security and which version, then enforce a policy on it.

References