openclaw-triage Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower

Source:

SHA-256:

openclaw-triage is an AI agent skill, created by atlaspa and published at atlaspa/openclaw-triage. ClawSecure audited openclaw-triage across 3 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 45/100 (High Risk). The 5 findings concentrate in Malicious Code and Permissions Manifest, including Suspicious domain detected: webhook.site (potential data exfiltration) and Attempts to access sensitive file: SOUL.md. 4 were rated high or critical severity.

Is openclaw-triage safe?

ClawSecure audited openclaw-triage and assigned a security score of 45/100 (High Risk), identifying 5 findings across Malicious Code and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in openclaw-triage?

ClawSecure identified 5 findings in openclaw-triage, concentrated in Malicious Code and Permissions Manifest. 4 were rated high or critical severity. The most severe include Suspicious domain detected: webhook.site (potential data exfiltration) and Attempts to access sensitive file: SOUL.md.

How was openclaw-triage audited?

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

What does a score of 45 mean?

ClawSecure assigned openclaw-triage a security score of 45/100, placing it in the High Risk range. This is driven by 5 findings led by Malicious Code that should be addressed before 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-triage

ClawSecure detected 5 security findings in openclaw-triage, spanning Malicious Code and Permissions Manifest.

critical · Suspicious domain detected: webhook.site (potential data exfiltration). Malicious Code finding detected in README.md.
high · Attempts to access sensitive file: SOUL.md. Malicious Code finding detected in README.md.
high · Attempts to access sensitive file: SOUL.md. Malicious Code finding detected in triage.py.
high · Attempts to access sensitive file: MEMORY.md. Malicious Code finding detected in triage.py.
medium · Missing config.json - agent may not be properly configured. Permissions Manifest finding.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for openclaw-triage

Audit external network connections

openclaw-triage 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 Agents→Beyond Static Scans: Why ClawSecure Verifies Agentic Intent→How to Secure an MCP Server: The 2026 Guide→

Related AI Agent Security Audits

ClawSecScore 45/100 claude-memScore 35/100 openclawScore 55/100 open-webuiScore 35/100 gnoScore 45/100

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