OpenClaw Security Audit
v1.0.0Security audit and credential hardening tool for OpenClaw instances. Scan for sensitive files, detect credential exposure, check gateway configuration, and m...
⭐ 0· 92·0 current·0 all-time
byLuoLuo&Big-fish@vincent-big-fish
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name, description, SKILL.md, and the included audit.py and harden.py are coherent: the files scan ~/.openclaw for sensitive files and credentials, check gateway config, back up and sanitize openclaw.json, and migrate found credentials to environment variables. No unrelated credentials, binaries, or services are requested.
Instruction Scope
Runtime instructions are limited to scanning and modifying files inside the OpenClaw directory and generating reports/backups. This matches the skill purpose, but the hardening step writes a plaintext .env file and replaces credentials in openclaw.json; the generated scripts then set environment variables. The SKILL.md claims no external transmission and the code contains no network calls.
Install Mechanism
No install spec; the skill is instruction-and-code-only and requires only running provided Python scripts. Nothing is downloaded or executed from external URLs during install, which reduces install-time risk.
Credentials
The skill requests no environment variables or external credentials. However, its hardening action intentionally extracts secret values and writes them to a local .env file and (via the generated Windows PowerShell script) can persist them into user environment variables. This is proportional to 'migrate to environment variables' but increases persistence and local exposure of secrets and should be treated as a security tradeoff.
Persistence & Privilege
The skill is not always-enabled and does not modify other skills. It does persist data in the user's home (~/.openclaw): backups, reports, .env, and setup scripts. On Windows the generated PowerShell script uses [Environment]::SetEnvironmentVariable(...,'User'), which writes persistent user-scoped environment variables (registry). This persistence is expected for the stated feature but has a lasting effect that users should review.
Assessment
This skill appears internally consistent and matches its description, but review and proceed cautiously: 1) The hardening step writes plaintext secrets to ~/.openclaw/.env and can create persistent user environment variables (Windows) — ensure you want secrets stored this way and secure the .env file. 2) Always review the generated .env, backup, and setup scripts before running them; run harden.py with dry-run first if available. 3) Keep backups from the skill and verify sanitized config before removing originals; rotate credentials after migration if you are concerned. 4) The package source is listed as "unknown" and has no homepage — prefer code from a known/trusted repository or inspect the full code locally before use. 5) Do not commit the generated .env to version control and restrict file permissions on backups, reports, and .env. If you want, run the audit first, inspect the JSON report, then run hardening in a test environment before applying to production.Like a lobster shell, security has layers — review code before you run it.
auditvk977naevtm3jesjaj9j18nqhmx836579credentialsvk977naevtm3jesjaj9j18nqhmx836579hardeningvk977naevtm3jesjaj9j18nqhmx836579latestvk977naevtm3jesjaj9j18nqhmx836579privacyvk977naevtm3jesjaj9j18nqhmx836579safetyvk977naevtm3jesjaj9j18nqhmx836579securityvk977naevtm3jesjaj9j18nqhmx836579
License
MIT-0
Free to use, modify, and redistribute. No attribution required.