sec-audit

对 OpenClaw 部署进行只读安全审计，检测环境泄露、认证配置、恶意 Skill 等已知风险和漏洞。

This package appears to implement an on-host OpenClaw security auditor and is mostly coherent with that purpose, but exercise caution before running it on sensitive systems: - Review the entire tools/security-audit.js file yourself (search for any HTTP/HTTPS/fetch/axios/request usage, or net/socket code). The snippet you provided was truncated; ensure the full file contains no network calls or remote upload logic. - Run the tool first in a safe/test environment or inside an isolated container/VM so it cannot access production secrets or exfiltrate data if there is hidden logic. - If you must run it on a host with secrets, run it after reducing available environment variables (unset secrets) or run with a clean environment: e.g., in a dedicated container with only necessary vars. - Inspect produced outputs (console and any --output file) before sharing them; the script masks env values but may still include partial identifiers. - If you plan to allow an agent to invoke this skill autonomously, restrict that agent’s permissions and review logs of when the skill is executed. If you want, I can scan the remainder of tools/security-audit.js (the truncated portion) for network calls or suspicious behavior — provide the full file and I will re-evaluate and may upgrade/downgrade the verdict.

Type: OpenClaw Skill Name: sec-audit Version: 1.0.0 This OpenClaw skill bundle is a security audit tool designed to detect vulnerabilities and malicious configurations within an OpenClaw deployment. The `SKILL.md` clearly states its purpose as 'read-only detection' and 'no data exfiltration', which is consistently supported by the `tools/security-audit.js` code. The script performs various legitimate security checks, including scanning for sensitive environment variables, plaintext credentials, insecure gateway configurations, known malicious skills/authors, suspicious patterns in `SKILL.md` and code files (e.g., Base64 encoded commands, reverse shells, known C2s), and system-level Indicators of Compromise (IOCs) using standard commands like `netstat`, `grep`, `shasum`, `ps aux`, and `crontab -l`. All `child_process.execSync` calls are for audit purposes with controlled inputs, and there is no evidence of intentional harmful behavior, data exfiltration to external endpoints, or prompt injection attempts against the agent running this skill.