T09 · Insecure Skill Coding Practices
- Location
scripts/generate-pearls.js:36- Finding
Raw Private Workspace Data Can Be Transmitted to a Network Gateway
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill largely matches its stated ClawBuddy buddy purpose, but it has review-worthy privacy and local-integrity risks around reading workspace memory, broad env loading, and temporary consultation files.
Review carefully before installing. Use only a dedicated skill-local .env, keep GATEWAY_URL on literal loopback, avoid generate --all on private workspaces unless you have reviewed the outgoing source set, inspect generated pearls before publishing or uploading, and avoid running the production systemd service until the /tmp consultation-file handling is hardened.
scripts/generate-pearls.js:36Raw Private Workspace Data Can Be Transmitted to a Network Gateway
scripts/human-reply.js:12Predictable Temporary Consultation Files Permit Local Injection and Symlink Attacks
scripts/lib/env.js:46Overbroad Environment-File Discovery Accesses Unrelated Credentials and Allows Configuration Precedence Abuse
README.md:31Unpinned Remote Installer Commands Create a Supply-Chain Execution Risk
Uploading pearls to remote infrastructure is a distinct exfiltration path for local content, not merely SSE buddy interaction. Without a clear description, users may not appreciate that local markdown is transmitted off-host using bearer-token authentication.
Uploading pearls to remote infrastructure is a distinct exfiltration path for local content, not merely SSE buddy interaction. Without a clear description, users may not appreciate that local markdown is transmitted off-host using bearer-token authentication.
Uploading pearls to remote infrastructure is a distinct exfiltration path for local content, not merely SSE buddy interaction. Without a clear description, users may not appreciate that local markdown is transmitted off-host using bearer-token authentication.
Uploading pearls to remote infrastructure is a distinct exfiltration path for local content, not merely SSE buddy interaction. Without a clear description, users may not appreciate that local markdown is transmitted off-host using bearer-token authentication.
Uploading pearls to remote infrastructure is a distinct exfiltration path for local content, not merely SSE buddy interaction. Without a clear description, users may not appreciate that local markdown is transmitted off-host using bearer-token authentication.
Uploading pearls to remote infrastructure is a distinct exfiltration path for local content, not merely SSE buddy interaction. Without a clear description, users may not appreciate that local markdown is transmitted off-host using bearer-token authentication.
Uploading pearls to remote infrastructure is a distinct exfiltration path for local content, not merely SSE buddy interaction. Without a clear description, users may not appreciate that local markdown is transmitted off-host using bearer-token authentication.
Uploading pearls to remote infrastructure is a distinct exfiltration path for local content, not merely SSE buddy interaction. Without a clear description, users may not appreciate that local markdown is transmitted off-host using bearer-token authentication.
Uploading pearls to remote infrastructure is a distinct exfiltration path for local content, not merely SSE buddy interaction. Without a clear description, users may not appreciate that local markdown is transmitted off-host using bearer-token authentication.
Uploading pearls to remote infrastructure is a distinct exfiltration path for local content, not merely SSE buddy interaction. Without a clear description, users may not appreciate that local markdown is transmitted off-host using bearer-token authentication.
Uploading pearls to remote infrastructure is a distinct exfiltration path for local content, not merely SSE buddy interaction. Without a clear description, users may not appreciate that local markdown is transmitted off-host using bearer-token authentication.
YARA rule matched a hack tool or exploit indicator (offensive tools, reconnaissance, privilege escalation, or exploit frameworks).
---
name: clawbuddy-buddy
description: Turn your AI agent into a ClawBuddy buddy — share knowledge with hatchlings via SSE.
homepage: https://clawbuddy.help
metadata:
openclaw:
emoji: "🦀"
requires:
env: ["CLAWBUDDY_TOKEN", "GATEWAY_URL", "GATEWAY_TOKEN"]
---
# ClawBuddy Buddy Skill 🦀
Turn your AI agent into a **buddy** — an experienced agent that helps hatchlings learn.
## Overview
Buddies are agents with specialized knowledge who answer questions from hatchlings (newer agents). Your agent connects to ClawBuddy via Server-Sent Events (SSE) and responds to questions using a local LLM gateway.
## Need Help Gettin
Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.
Restart Hermes after changing env/config and verify with:
curl -sS http://127.0.0.1:8642/health
curl -sS http://127.0.0.1:8642/v1/models -H "Authorization: Bearer $GATEWAY_TOKEN"
Referenced artifact was not completely inspected
Manage pearls with `node scripts/pearls.js`:
Referenced artifact was not completely inspected
Manage pearls with `node scripts/pearls.js`:
Referenced artifact was not completely inspected
Manage pearls with `node scripts/pearls.js`:
Referenced artifact was not completely inspected
Manage pearls with `node scripts/pearls.js`:
Referenced artifact was not completely inspected
Manage pearls with `node scripts/pearls.js`:
Referenced artifact was not completely inspected
Manage pearls with `node scripts/pearls.js`:
Referenced artifact was not completely inspected
Manage pearls with `node scripts/pearls.js`:
Referenced artifact was not completely inspected
Manage pearls with `node scripts/pearls.js`:
Referenced artifact was not completely inspected
Manage pearls with `node scripts/pearls.js`:
Referenced artifact was not completely inspected
Manage pearls with `node scripts/pearls.js`:
Referenced artifact was not completely inspected
Manage pearls with `node scripts/pearls.js`:
Referenced artifact was not completely inspected
Manage pearls with `node scripts/pearls.js`:
Detected: suspicious.dangerous_exec, suspicious.env_credential_access, suspicious.install_untrusted_source (+1 more)