← Back to Scanner

emergency-rescue Security Audit Report

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

emergency-rescue is an AI agent skill, created by gitgoodordietrying and published at openclaw/skills. ClawSecure audited emergency-rescue across 2 files through the 3-Layer Audit Protocol covering all ten OWASP ASI Top 10 categories, assigning a security score of 65/100 (Medium Risk). The 4 findings concentrate in Policy Violation, Hardcoded Secrets and Permissions Manifest, including Pattern detected: AKIAXXXXXXXXXXXXXXXX and Attempts to access sensitive file: .ssh/. 2 were rated high or critical severity.

Is emergency-rescue safe?

ClawSecure audited emergency-rescue and assigned a security score of 65/100 (Medium Risk), identifying 4 findings across Policy Violation and Hardcoded Secrets. Review the findings below before installing.

What did ClawSecure find in emergency-rescue?

ClawSecure identified 4 findings in emergency-rescue, concentrated in Policy Violation, Hardcoded Secrets and Permissions Manifest. 2 were rated high or critical severity. The most severe include Pattern detected: AKIAXXXXXXXXXXXXXXXX and Attempts to access sensitive file: .ssh/.

How was emergency-rescue audited?

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

What does a score of 65 mean?

ClawSecure assigned emergency-rescue a security score of 65/100, placing it in the Medium Risk range. This reflects 4 findings led by Policy Violation 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 emergency-rescue

ClawSecure detected 4 security findings in emergency-rescue, spanning Policy Violation, Hardcoded Secrets, Permissions Manifest and Malicious Code.

Each finding is expandable in the interactive list below.

3-Layer Audit Protocol

Security Recommendations for emergency-rescue

Resolve policy violations
emergency-rescue 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
emergency-rescue 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

gitlab-cli-skillsScore 55/100devops-mainScore 75/100devops-mainScore 75/100devops-mainScore 75/100redditScore 80/100

Scanned on February 7, 2026. emergency-rescue 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