gno Security Audit Report

🔭 Continuously monitored by ClawSecure Watchtower

Source:

SHA-256:

gno is an AI agent skill, created by gmickel and published at gmickel/gno. ClawSecure audited gno across 50 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 25/100 (Critical). The 9 findings concentrate in Malicious Code, Code Injection and ReDoS, including Attempts to access sensitive file: MEMORY.md and Attempts to access sensitive file: MEMORY.md. 6 were rated high or critical severity.

Is gno safe?

ClawSecure audited gno and assigned a security score of 25/100 (Critical), identifying 9 findings across Malicious Code and Code Injection. Review the findings below before installing.

What did ClawSecure find in gno?

ClawSecure identified 9 findings in gno, concentrated in Malicious Code, Code Injection and ReDoS. 6 were rated high or critical severity. The most severe include Attempts to access sensitive file: MEMORY.md and Attempts to access sensitive file: MEMORY.md.

How was gno audited?

ClawSecure ran gno through its 3-Layer Audit Protocol with full OWASP ASI Top 10 coverage, scanning 50 files from gmickel/gno.

What does a score of 25 mean?

ClawSecure assigned gno a security score of 25/100, placing it in the Critical range. This is driven by 9 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 gno

ClawSecure detected 9 security findings in gno, spanning Malicious Code, Code Injection, ReDoS and Permissions Manifest.

high · Attempts to access sensitive file: MEMORY.md. Malicious Code finding detected in SKILL.md.
high · Attempts to access sensitive file: MEMORY.md. Malicious Code finding detected in cli-reference.md.
high · Attempts to access sensitive file: MEMORY.md. Malicious Code finding detected in SKILL.md.
high · Attempts to access sensitive file: MEMORY.md. Malicious Code finding detected in cli-reference.md.
high · Potentially dangerous code pattern detected: curl.*\|.*sh. Code Injection finding detected in README.md.
high · Potentially dangerous code pattern detected: eval\(. Code Injection finding detected in CLAUDE.md.
medium · Missing config.json - agent may not be properly configured. Permissions Manifest finding.
medium · ReDoS vulnerability: Nested quantifiers (potential…. ReDoS finding detected in cli-reference.md:1112.
medium · ReDoS vulnerability: Nested quantifiers (potential…. ReDoS finding detected in cli-reference.md:1112.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for gno

Audit external network connections

gno 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.

Eliminate dynamic code execution

gno evaluates code at runtime (for example eval or dynamic exec). Remove dynamic evaluation of untrusted input, and where code generation is unavoidable, sandbox it and validate every input.

Fix ReDoS-prone patterns

gno contains regular expressions vulnerable to catastrophic backtracking (ReDoS). Replace vulnerable patterns, bound input length, and prefer linear-time matching so a crafted input cannot hang the agent.

Related Security Research

ClawHavoc Explained: The Malware Family Targeting AI Agents→Beyond Static Scans: Why ClawSecure Verifies Agentic Intent→

Related AI Agent Security Audits

fzfScore 25/100 open-webuiScore 35/100 fzfScore 25/100 fzfScore 25/100 ai-skillsScore 35/100

Scanned on October 21, 2026. gno 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