T08 · Insecure Dependencies
- Location
SKILL.md:43- Finding
Unverified Third-Party Package Execution Through Generated Installation Commands
- Content
View full analysis
`. - Include a no-install fallback: inspect the skill page and copy the usage prompt. - Do not claim downloads, stars, ratings, or review status unless provided. ``` The corresponding command is generated in `scripts/install_bridge.py`, line 44: ```python command = f"npx --yes clawhub@0.9.0 install {slug}" ``` ### Technical Analysis The Skill generates documentation that instructs users to invoke `npx` with the `--yes` option. This causes npm to retrieve and execute `clawhub@0.9.0` without an interactive installation confirmation. Pinning the package version reduces unexpected version drift, but it does not verify the integrity or provenance of the retrieved artifact. The generated command does not specify an expected package digest, a verified local artifact, or an explicitly trusted registry. Its security therefore depends on the npm registry, package maintainer account, package metadata, and client-side registry configuration. The project itself does not fetch or execute this dependency. The exposure occurs when a user follows the generated installation instructions. ### Attack Path 1. An attacker compromises the publisher account, package distribution infrastructure, or registry path used to resolve `clawhub@0.9.0`. 2. Alternatively, an attacker influences the user's npm registry configuration so that the package resolves from an untrusted registry. 3. The Skill generates the command `npx --yes clawhub@0.9.0 install `. 4. A user copies and runs the generated command. 5. `npx` downloads the resolved package and executes its entry point without an interactive confirmation. 6. Malicious package ...[truncated 803 chars]- Remediation
View remediation
