← Back to Scanner

openclaw-security Security Audit Report

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

openclaw-security is an AI agent skill, created by atlaspa and published at atlaspa/openclaw-security. ClawSecure audited openclaw-security across 3 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 85/100 (Safe). The 3 findings concentrate in Policy Violation, Permissions Manifest and Malicious Code, including Attempts to access sensitive file: MEMORY.md and Missing config.json - agent may not be properly configured. 1 was rated high or critical severity.

Is openclaw-security safe?

ClawSecure audited openclaw-security and assigned a security score of 85/100 (Safe), identifying 3 findings across Policy Violation and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in openclaw-security?

ClawSecure identified 3 findings in openclaw-security, concentrated in Policy Violation, Permissions Manifest and Malicious Code. 1 was rated high or critical severity. The most severe include Attempts to access sensitive file: MEMORY.md and Missing config.json - agent may not be properly configured.

How was openclaw-security audited?

ClawSecure ran openclaw-security through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 3 files from atlaspa/openclaw-security.

What does a score of 85 mean?

ClawSecure assigned openclaw-security a security score of 85/100, placing it in the Safe range. Scores of 80 or above qualify for ClawSecure Verified status, though 1 finding was rated high or critical and warrants review. 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-security

ClawSecure detected 3 security findings in openclaw-security, spanning Policy Violation, Permissions Manifest and Malicious Code.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for openclaw-security

Resolve policy violations
openclaw-security trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
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-security 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

OWASP ASI Top 10 Explained: The Complete Guide to AI Agent Security StandardsUnderstanding Our 3-Layer Audit ProtocolHow to Secure an MCP Server: The 2026 Guide

Related AI Agent Security Audits

Anthropic-Cybersecurity-SkillsScore 70/100imsgScore 95/100antigravity-awesome-skillsScore 75/100GitNexusScore 75/100wacliScore 95/100

Scanned on May 4, 2026. openclaw-security 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