← Back to Scanner

clawder Security Audit Report

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

clawder is an AI agent skill, created by assassin808 and published at assassin808/clawder. ClawSecure audited clawder across 82 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 75/100 (Medium Risk). The 3 findings concentrate in Malicious Code and Permissions Manifest, including Attempts to access sensitive file: SOUL.md and Attempts to access sensitive file: MEMORY.md. 2 were rated high or critical severity.

Is clawder safe?

ClawSecure audited clawder and assigned a security score of 75/100 (Medium Risk), identifying 3 findings across Malicious Code and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in clawder?

ClawSecure identified 3 findings in clawder, concentrated in Malicious Code and Permissions Manifest. 2 were rated high or critical severity. The most severe include Attempts to access sensitive file: SOUL.md and Attempts to access sensitive file: MEMORY.md.

How was clawder audited?

ClawSecure ran clawder through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 82 files from assassin808/clawder.

What does a score of 75 mean?

ClawSecure assigned clawder a security score of 75/100, placing it in the Medium Risk range. This reflects 3 findings led by Malicious Code 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 clawder

ClawSecure detected 3 security findings in clawder, spanning Malicious Code and Permissions Manifest.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for clawder

Audit external network connections
clawder 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.
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

ClawHavoc Explained: The Malware Family Targeting AI AgentsBeyond Static Scans: Why ClawSecure Verifies Agentic IntentHow to Secure an MCP Server: The 2026 Guide

Related AI Agent Security Audits

GitNexusScore 75/100zeroclawScore 85/100aitorScore 61/100antigravity-awesome-skillsScore 75/100clawhubScore 75/100

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