← Back to Scanner

openclaw-config-validator Security Audit Report

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

openclaw-config-validator is an AI agent skill, created by charpup and published at charpup/openclaw-config-validator. ClawSecure audited openclaw-config-validator across 27 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 65/100 (Medium Risk). The 4 findings concentrate in Code Injection, Permissions Manifest and Malicious Code, including Attempts to access sensitive file: SOUL.md and Potentially dangerous code pattern detected: exec\(. 3 were rated high or critical severity.

Is openclaw-config-validator safe?

ClawSecure audited openclaw-config-validator and assigned a security score of 65/100 (Medium Risk), identifying 4 findings across Code Injection and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in openclaw-config-validator?

ClawSecure identified 4 findings in openclaw-config-validator, concentrated in Code Injection, Permissions Manifest and Malicious Code. 3 were rated high or critical severity. The most severe include Attempts to access sensitive file: SOUL.md and Potentially dangerous code pattern detected: exec\(.

How was openclaw-config-validator audited?

ClawSecure ran openclaw-config-validator through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 27 files from charpup/openclaw-config-validator.

What does a score of 65 mean?

ClawSecure assigned openclaw-config-validator a security score of 65/100, placing it in the Medium Risk range. This reflects 4 findings led by Code Injection that warrant review before production use. 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 openclaw-config-validator

ClawSecure detected 4 security findings in openclaw-config-validator, spanning Code Injection, Permissions Manifest and Malicious Code.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for openclaw-config-validator

Eliminate dynamic code execution
openclaw-config-validator evaluates code at runtime (for example eval or dynamic exec). Remove dynamic evaluation of untrusted input, and where code generation is unavoidable, sandbox it and validate every input.
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.
Audit external network connections
openclaw-config-validator connects to external endpoints. Verify every outbound connection goes to a trusted destination. Unauthorized callbacks are a primary indicator of ClawHavoc malware and data exfiltration. ClawSecure's proprietary engine monitors for known malicious endpoints including C2 infrastructure.
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 SecurityBeyond Static Scans: Why ClawSecure Verifies Agentic IntentHow to Secure an MCP Server: The 2026 Guide

Related AI Agent Security Audits

c81972687d0e5a06Score 75/1007caf5d769dee89c3Score 55/10049d9c51b3ba29229Score 75/10019af8eafb16b72f6Score 75/1003f5bb9462d7cb920Score 75/100

Scanned on March 1, 2026. openclaw-config-validator 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