OpenClaw skill security: what the launch data says for teams

TL;DR: A broader AI agent security problem surfaced in ClawSecure's Product Hunt launch, with 41% of 2,890+ audited OpenClaw skills showing vulnerabilities, 9,515 findings in total, and 539 skills carrying malware indicators, according to ClawSecure. The pattern is clear: runtime trust cannot be assumed after installation, because agentic workflows can turn approved skills into concealed access paths.

Editorial analysis by NHI Mgmt Group, based on content published by ClawSecure: “ClawSecure Reached #2 Product of the Day on Product Hunt”.

By the numbers:

• ClawSecure recorded 1,498 new users scanning agents through the platform on launch day.
• ClawSecure found that 41% of popular OpenClaw skills have security vulnerabilities.
• ClawSecure detected 9,515 total security findings across the audited dataset.

Key questions

Q: What breaks when AI agent skills are treated like documentation instead of runtime policy?

A: The review model breaks because the agent consumes skill instructions as operational input, not as explanatory text.

Q: Why do approved agent skills still create security risk after scanning?

A: Scanning only tells you what was visible at one point in time.

Q: How should security teams manage permissions for AI agents?

A: Security teams should regularly assess and update the permissions granted to AI agents to ensure they align with their intended scope.

Practitioner guidance

• Define agent skills as governed identities Classify each OpenClaw skill by the authority it can exercise, including filesystem, clipboard, shell, and other tool permissions, then assign an owner and review cadence.
• Gate installation on delegated authority review Require a pre-install approval step that checks what the skill can do at runtime, not just whether its code scans cleanly or its repository looks reputable.
• Monitor approved skills for post-install change Track code, dependencies, and observed behaviour after deployment so a later update or hidden action cannot silently expand the skill's access path.

Bottom line: AI agent skills create a governance problem because their authority continues after installation, when they can still reach files, shells, and clipboard data.

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →