OpenA2A Security

Security hardening for OpenClaw. Audit your configuration, scan installed skills for malware, detect CVE-2026-25253, check credential exposure, and get actio...

This skill looks like an on-demand local auditor, but proceed cautiously: (1) The SKILL.md tells the agent to run 'npx hackmyagent' — npx will typically fetch code from the npm registry at runtime, which contradicts the claim 'runs entirely locally' and means remote code could be executed. (2) There is no source/homepage or pinned package/version/checksum provided — you cannot verify the exact code that will run. Recommended next steps before installing/using: a) Verify provenance of 'hackmyagent' (npm package page, repository, maintainer) and prefer a pinned, audited release; b) If possible, vendor the scanner locally (install the package yourself and inspect it) or run the commands manually in a controlled sandbox; c) Run the scanner in an isolated environment (container or VM) and review generated output before allowing any automation to act on it; d) Ask the publisher for a homepage, repository link, and a signed checksum or pinned version; e) If you must run via npx, consider network controls or npm cache use and inspect package contents (npm pack) beforehand. If the author can supply a repository link, pinned version, and checksum, or provide a vendored copy of hackmyagent, the concerns would be largely mitigated.

Type: OpenClaw Skill Name: opena2a-security Version: 1.0.0 This skill is designed for security auditing and hardening of OpenClaw installations. Its stated purpose is to scan for vulnerabilities, malware, and credential exposure, which is a legitimate security function. The `SKILL.md` explicitly declares `permissions.network: []`, ensuring no external API calls, and `permissions.exec` is limited to `npx hackmyagent`, which is the open-source security scanner it uses. All instructions for the AI agent are transparent, directly related to security scanning, and lack any evidence of prompt injection, data exfiltration, obfuscation, or other malicious intent. The requested filesystem access to `~/.openclaw` is necessary and appropriate for its stated security auditing purpose.