Security Audit Report
binance Security Audit Report
🔭 Continuously monitored by ClawSecure Watchtower
binance is a Other skill for the OpenClaw ecosystem, created by 0xterrybit. ClawSecure audited this skill through our 3-Layer Audit Protocol covering all 10 OWASP ASI Top 10 categories. This skill received a security score of 55/100, indicating moderate risk areas that should be addressed. The audit identified 4 findings across the scan's three security layers.
What does a score of 55 mean?
A security score of 55/100 places this skill in the Medium Risk range. Skills in this range have identifiable security concerns that may need remediation before production use. Review the findings below and consider the specific recommendations provided. ClawSecure calculates scores using a weighted deduction model: critical findings deduct 20 points, high-severity findings deduct 10, medium-severity 5, and low-severity 2. A perfect score of 100 means no findings were detected across all three audit layers.
✓ You're subscribed to Watchtower alerts for this skill.
🏛️
OWASP ASI Framework Coverage
Categories highlighted were detected in this scan. ClawSecure provides comprehensive coverage across all 10 OWASP ASI Top 10 categories.
🎯Context-Aware Analysis
This skill requests system-level capabilities which are standard for OpenClaw automation skills. Generic scanners often flag these capabilities as suspicious regardless of context. ClawSecure's Context-Aware Intelligence analyzes capabilities in ecosystem context — we differentiate real threats (malicious code, unauthorized data exfiltration, supply chain vulnerabilities, ReDoS patterns) from normal agent functionality. Our 3-Layer Audit Protocol is purpose-built for the OpenClaw ecosystem.
🏛️ Findings are tagged with OWASP ASI (Agentic Security Initiative) Top 10 category references where applicable. ClawSecure provides comprehensive coverage across all 10 OWASP ASI categories. Learn more at owasp.org
Security Recommendations for binance
Pin npm dependencies to exact versions
Unpinned dependencies allow supply chain attacks where a compromised package version is automatically pulled into your skill. Use exact version numbers in package.json (e.g., 1.2.3 instead of ^1.2.3) to prevent unauthorized code from entering your dependency tree. ClawSecure's supply chain scanning checks every dependency against known CVE databases.
Add a config.json permissions manifest
A config.json file declares what permissions your OpenClaw skill needs — file system access, network requests, shell execution, and more. Without it, users have no visibility into what your skill can do before installing. Adding a permissions manifest is the single most impactful security improvement for any OpenClaw skill.
Review credential handling
Hardcoded credentials in source code are a critical security risk. API keys, tokens, and passwords should never appear in skill files. Use environment variables or secure credential storage instead. If credentials have been committed to a public repository, rotate them immediately — they should be considered compromised.
Related Other Security Audits
Scanned on February 7, 2026. binance is one of 2,890+ agents audited by ClawSecure from the community-curated awesome-openclaw-skills list and the openclaw/skills repository.