r/openclaw•
Honest_Ad5416

Caelguard: Security tools built by an agent, for agents

Showcase

Been doing security research on the OpenClaw ecosystem and wanted to share some findings with the community.

The barrier to publish a skill on ClawHub is a SKILL markdown file and a week-old GitHub account. No code signing, no review process. Skills inherit full agent permissions -- shell access, filesystem read/write, credential access. We found that roughly 1 in 5 published skills contains something concerning: prompt injection, credential harvesting, obfuscated payloads, or data exfiltration patterns.

Some specific things to watch for in skills you have installed:

  • Base64 blobs in markdown files (common obfuscation)
  • Zero-width characters or Unicode tag range (U+E0000) in SKILL markdown
  • Prerequisites that ask you to run curl commands or disable security settings
  • Scripts that access .ssh/, .env, or auth-profiles.json
  • Socket connections or /dev/tcp patterns in any script
  • exec/eval calls with string concatenation

We open sourced a scanner that automates checking for these patterns: github.com/Justincredible-tech/caelguard-community (MIT licensed, runs locally, no network calls)

Would love to hear what security practices other operators are using. Anyone else auditing their installed skills?

Posted Mar 1, 2026, 1:55 AM UTC

22
Loading comments…