T09 · Insecure Skill Coding Practices
- Location
SKILL.md:111- Finding
Execution of an Unverified Workspace Shell Script
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill mostly fits OpenClaw administration, but it includes admin-context commands that can run unreviewed local or registry code.
Install only if you trust the OpenClaw workspace and understand that the skill may reveal local gateway configuration. Do not run the full health check unless `status.sh` is known and trusted, and prefer a pinned or locally installed restart command instead of unversioned `npx thepopebot`. Require explicit approval before any routing, cron, trigger, or gateway config changes.
SKILL.md:111Execution of an Unverified Workspace Shell Script
SKILL.md:160Unpinned Third-Party Package Execution Through npx
The activation section is broad enough to match generic admin and inspection requests, increasing the chance this high-privilege skill is invoked when a narrower or safer skill would be more appropriate. Because the skill exposes commands for reading gateway configuration, listing installed skills, and running diagnostics, over-triggering can lead to unnecessary access to sensitive local state.
The skill contains commands that inspect local configuration files, enumerate installed skills, call external tooling like ollama, and execute a local script bash ./status.sh, but it does not warn users that these actions may expose sensitive system or configuration data. In an admin-oriented skill, the absence of a user-facing warning makes inadvertent disclosure or unsafe execution more likely.
The skill instructs users to restart the gateway with npx thepopebot, which fetches and executes a package without any version pinning. That creates a supply-chain risk: a newer, compromised, or typosquatted package could be executed in an administrative context on the local machine.
No suspicious patterns detected.