← Back to Scanner

section11 Security Audit Report

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

section11 is an AI agent skill, created by crankaddict and published at openclaw/skills. ClawSecure audited section11 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: SOUL.md and Missing config.json - agent may not be properly configured. 1 was rated high or critical severity.

Is section11 safe?

ClawSecure audited section11 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 section11?

ClawSecure identified 3 findings in section11, 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: SOUL.md and Missing config.json - agent may not be properly configured.

How was section11 audited?

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

What does a score of 85 mean?

ClawSecure assigned section11 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 section11

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

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for section11

Resolve policy violations
section11 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
section11 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 Standards→Understanding Our 3-Layer Audit Protocol→How to Secure an MCP Server: The 2026 Guide→

Related AI Agent Security Audits

ui-ux-pro-max-skillScore 75/100lossless-clawScore 85/100imsgScore 95/100wacliScore 95/100GitNexusScore 75/100

Scanned on April 23, 2026. section11 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