T08 · Insecure Dependencies
- Location
references/skill-search.md:76- Finding
Third-Party Skills Are Installed Before Security Review
- Content
View full analysis
-g -y ``` **ClawHub:** ```bash clawhub install ``` ``` The security audit occurs only after installation: ```bash ## Step 7: Security Audit Run automated security audit on installed skill: ```bash python scripts/audit_skill.py --skill ./skills/ --output ${OUTPUT_DIR}/02-audit.md ``` ``` ### Technical Analysis The workflow installs skills obtained from external registries before inspecting their contents. The Skills.sh command is global and non-interactive because it uses `-g -y`. The ClawHub command similarly installs a registry-selected skill before the local audit is performed. A post-installation static scan cannot protect against code executed during package resolution, installation hooks, CLI behavior, or other installer-controlled operations. If a registry package or one of its dependencies is malicious or compromised, code may execute before `audit_skill.py` has an opportunity to reject it. The automated audit is also only a pattern-based scanner. It does not establish package provenance, verify immutable digests, inspect dependency graphs, or prevent installation-time execution. ### Attack Path 1. An attacker publishes a malicious skill or compromises an existing registry skill. 2. The malicious skill is returned by `npx skills find` or `clawhub search`. 3. The user selects the skill through the documented checkpoint. 4. The workflow runs `npx skills add -g -y` or `clawhub install `. 5. The registry client, package installer, or installation hooks execute attacker-controlled code with the invoking user's privileges. 6. The security aud ...[truncated 793 chars]- Remediation
View remediation
