Openclaw Defender

Provides real-time file integrity monitoring, pre-installation skill audits, runtime threat blocking, kill switch activation, and incident response to protec...

This package mostly looks like a sensible defender toolkit, but before you enable it or wire it into your agent: 1) Inspect scripts/runtime-monitor.sh and update-lists.sh for any outbound network calls, hard-coded endpoints, or remote code execution; do not run generate-baseline.sh until you are sure your workspace is in a known-good state (creating a baseline from compromised files can lock in malicious state). 2) Do not add the cron job or integrate runtime-monitor hooks into OpenClaw core until you've audited the scripts (run them in an isolated/sandbox environment first). 3) Treat external update sources as hostile by default — either pin the blocklist source to a trusted repo you control or review fetched data before applying. 4) Verify the publisher/repository provenance (owner identity, GitHub repo activity) — absence of a clear homepage/author is a risk. 5) If you lack time/expertise to audit the runtime-monitor script, consider running audit-only features (scripts that scan skills) manually and delaying automated runtime enforcement. Following these steps will materially reduce supply-chain and persistence risk.

Type: OpenClaw Skill Name: openclaw-defender Version: 0.1.0 This skill bundle, 'openclaw-defender', is a comprehensive security framework designed to protect OpenClaw agents from various attacks, including prompt injection, credential theft, and data exfiltration. All analyzed files (scripts, documentation, and metadata) consistently describe defensive measures, threat detection, and incident response. The scripts like `runtime-monitor.sh` actively block dangerous commands, network requests to known malicious infrastructure (e.g., 91.92.242.30, glot.io), and file access to sensitive areas. The `audit-skills.sh` script scans for malicious patterns like base64 encoding, `curl|bash`, and prompt injection phrases, which are documented as threats, not executed by the skill itself. The `update-lists.sh` script legitimately uses `curl` or `wget` to fetch blocklists from a specified GitHub repository, which is a standard practice for updating threat intelligence in a security tool. There is no evidence of intentional harmful behavior; instead, the skill is explicitly designed to prevent such actions.