Topic starter
02/08/2026 12:00 pm
TL;DR: Malicious Claude Skills on ClawHub are being distributed through fake AI personas and used for crypto scams and private key theft, according to Straikerai research, turning skill marketplaces into an active supply chain attack surface. Autonomous execution makes published skills a governance problem, because trust can be abused without a human approval step.
Editorial analysis by NHI Mgmt Group, based on content published by Straikerai: “Built on ClawHub, Spread on Moltbook: The New Agent-to-Agent Attack Chain”.
Key questions
Q: What breaks when a skill marketplace is treated like a trusted app store?
A: The control that breaks is the assumption that publication equals safety.
Q: Why do AI coding agents increase supply-chain risk?
A: AI coding agents can choose tooling, install packages, and edit lock files in ways that may bypass the controls humans expect in a managed environment.
Q: How can security teams tell when a skill marketplace is failing governance controls?
A: Look for symptoms such as broad default permissions, opaque external endpoints, shell invocation inside skill code, and no mandatory review before publication.
Practitioner guidance
- Audit skill provenance before deployment Require source review, publisher verification, and dependency inspection before any skill is allowed into a production agent workflow.
- Enforce execution-time permission scoping Bind each skill to the smallest possible API, file, and network permissions, and block runtime escalation beyond that scope.
- Isolate first use in monitored environments Run new skills in contained test environments and watch for unexpected network calls, file access, or credential handling before broad rollout.
Bottom line: Malicious AI skills turn a discovery marketplace into a delegated execution channel, which expands the security problem from software hygiene to identity governance.
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
02/08/2026 1:07 pm
Agent skill marketplaces are now a supply-chain control point, not a convenience layer: once a skill can influence tool use, API calls, and external actions, it becomes part of the identity control plane. That shifts governance from code review alone to provenance, permission scoping, and publisher trust. The practitioner conclusion is simple: if the marketplace can deploy capability, it also needs security-grade lifecycle control.
A question worth separating out:
Q: What should organisations do after discovering a malicious AI skill?
A: They should revoke the skill, inspect downstream agent activity, and identify any credentials, APIs, or transaction paths the skill could have touched. The response should treat the event as a supply-chain compromise, not just a bad plugin. That means containment, lineage review, and restoration of trust boundaries.
👉 Read our full editorial: Agent-to-agent skill marketplaces are becoming a supply chain risk