Ai Security Audit

ReviewAudited by ClawScan on May 10, 2026.

Overview

The skill is a mostly instruction-only security-audit guide, but its core claim that it queries OpenClaw threat intelligence is not backed by any declared API, tool, credential, or install mechanism.

Before installing or using this skill, ask how it actually accesses the claimed OpenClaw threat-intelligence database. Treat any generated security findings as advisory unless the agent provides verifiable source data. If you use the hardening commands, run them manually and carefully on the intended host only.

Findings (2)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

A user may trust a security report that appears data-driven even if the agent cannot verify the endpoint against the claimed threat-intelligence source.

Why it was flagged

The skill makes strong database-backed security claims, but the supplied artifacts show no API, credential, code, install spec, or capability signal that would allow the agent to actually query or verify that database.

Skill content
This skill performs a structured security audit ... against the OpenClaw threat intelligence database, which currently tracks **278,230+ exposed AI endpoints** worldwide.
Recommendation

Only rely on reported breach, credential-leak, APT, or CVE associations if the skill or agent clearly shows the source, query method, and retrieved evidence.

What this means

Running the suggested commands incorrectly could block legitimate access to the service or lock out users.

Why it was flagged

The skill documents privileged firewall commands as remediation steps. They are aligned with the audit purpose, but they can affect server connectivity if copied without review.

Skill content
sudo ufw deny 18789 ... sudo ufw allow from <your-office-ip> to any port 18789 ... iptables -A INPUT -p tcp --dport 18789 -j DROP
Recommendation

Review firewall changes carefully, replace placeholders with the correct trusted IP ranges, and test access before applying permanent rules.