← Back to Scanner

probe-05-memory-read Security Audit Report

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

probe-05-memory-read is an AI agent skill. ClawSecure audited probe-05-memory-read across 2 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 4 findings concentrate in Malicious Code, Permissions Manifest and Policy Violation, including Attempts to access sensitive file: SOUL.md and Attempts to access sensitive file: MEMORY.md. 2 were rated high or critical severity.

Is probe-05-memory-read safe?

ClawSecure audited probe-05-memory-read and assigned a security score of 75/100 (Medium Risk), identifying 4 findings across Malicious Code and Permissions Manifest. Review the findings below before installing.

What did ClawSecure find in probe-05-memory-read?

ClawSecure identified 4 findings in probe-05-memory-read, concentrated in Malicious Code, Permissions Manifest and Policy Violation. 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 probe-05-memory-read audited?

ClawSecure ran probe-05-memory-read through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 2 files.

What does a score of 75 mean?

ClawSecure assigned probe-05-memory-read a security score of 75/100, placing it in the Medium Risk range. This reflects 4 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 probe-05-memory-read

ClawSecure detected 4 security findings in probe-05-memory-read, spanning Malicious Code, Permissions Manifest and Policy Violation.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for probe-05-memory-read

Audit external network connections
probe-05-memory-read 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.
Resolve policy violations
probe-05-memory-read trips ClawSecure policy checks. Review each flagged pattern against your security policy and remediate or document an accepted exception before production use.
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

hermes-agentScore 85/100Agent-ReachScore 85/100agent-skillsScore 85/100agent-creditScore 75/100Agent-ReachScore 75/100

Scanned on March 30, 2026. probe-05-memory-read 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