← Back to Scanner

bd2aa53d1889dd92 Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower
Source:
SHA-256:

bd2aa53d1889dd92 is an AI agent skill, created by 666ghj and published at 666ghj/MiroFish. ClawSecure audited bd2aa53d1889dd92 across 50 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 80/100 (Safe). The 4 findings concentrate in ReDoS and Permissions Manifest, including Missing config.json - agent may not be properly configured and ReDoS vulnerability: Nested quantifiers (potential…. None were rated high or critical severity.

Is bd2aa53d1889dd92 safe?

ClawSecure audited bd2aa53d1889dd92 and assigned a security score of 80/100 (Safe), identifying 4 findings across ReDoS and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in bd2aa53d1889dd92?

ClawSecure identified 4 findings in bd2aa53d1889dd92, concentrated in ReDoS and Permissions Manifest. The most severe include Missing config.json - agent may not be properly configured and ReDoS vulnerability: Nested quantifiers (potential….

How was bd2aa53d1889dd92 audited?

ClawSecure ran bd2aa53d1889dd92 through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 50 files from 666ghj/MiroFish.

What does a score of 80 mean?

ClawSecure assigned bd2aa53d1889dd92 a security score of 80/100, placing it in the Safe range. Scores of 80 or above qualify for ClawSecure Verified status; the 4 findings detected are lower-severity. ClawSecure derives this score with a weighted deduction model (critical -20, high -10, medium -5, low -2 from a base of 100).

Audit Findings for bd2aa53d1889dd92

ClawSecure detected 4 security findings in bd2aa53d1889dd92, spanning ReDoS and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for bd2aa53d1889dd92

Fix ReDoS-prone patterns
bd2aa53d1889dd92 contains regular expressions vulnerable to catastrophic backtracking (ReDoS). Replace vulnerable patterns, bound input length, and prefer linear-time matching so a crafted input cannot hang the agent.
Add a config.json permissions manifest
A config.json file declares what an agent component can access: file system, network, shell execution and more. Without it, users have no visibility into what the component can do before installing. This is the single most impactful security improvement for any AI agent skill.
Pin dependencies to exact versions
Unpinned dependencies allow supply-chain attacks where a compromised version is pulled in automatically. Use exact version numbers in package.json (for example 1.2.3 instead of ^1.2.3) to keep unauthorized code out of your dependency tree. ClawSecure checks every dependency against known CVE databases.

Related Security Research

Why Generic Scanners Fail at AI Agent Security→Understanding Our 3-Layer Audit Protocol→How to Secure an MCP Server: The 2026 Guide→

Related AI Agent Security Audits

playwright-best-practicesScore 95/1006fb89c3f86a53456Score 95/100b4abd97bcb77151aScore 75/10030bdbb41c9aa6d07Score 95/100624aee5f17bf59b1Score 95/100

Scanned on July 21, 2026. bd2aa53d1889dd92 is one of thousands of agents audited by ClawSecure from the community-curated awesome-openclaw-skills list and the openclaw/skills repository.

Start Your Free Scan