T08 · Insecure Dependencies
- Location
SKILL.md:17- Finding
Installation Commands Execute Unpinned Third-Party Packages
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:17,README.md:26, andREADME.md:32
Vulnerability Type: Unpinned and unverified third-party dependency execution
Risk Level: MediumVulnerable Code
SKILL.md:16-18:bash npx clawhub@latest install project-documentationREADME.md:25-27:bash npx add https://github.com/wpank/ai/tree/main/skills/meta/project-documentationREADME.md:31-33:bash npx clawhub@latest install project-documentationTechnical Analysis
The documented installation procedures use
npx, which can download and execute npm package code on the local system. The commandnpx clawhub@latestexplicitly selects a mutable package release rather than a reviewed, exact version. Consequently, the code executed during installation can differ from the code that existed when this skill was audited.The
npx addcommand also executes an unpinned npm package namedaddand supplies a GitHub tree URL that is not tied to an immutable commit. Neither command specifies an expected integrity hash, verified package artifact, lockfile, or validation procedure.This is a supply-chain weakness rather than evidence that the current upstream packages are malicious. Exploitation depends on an upstream package, publisher account, registry distribution path, or referenced repository being compromised or unexpectedly modified.
Attack Path
- An attacker compromises the publisher account, release process, registry package, or mutable repository reference used by the installation command.
- The attacker publishes a modified release under the package name or changes content reached through the mutable source reference.
- A user follows the installation instructions and runs one of the documented
npxcommands. npxdownloads the current, unreviewed package implementation.- The package CLI or associated lifecycle code executes with the privileges an ...[truncated 1081 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace
clawhub@latestwith an explicitly reviewed package version. - Generate and publish an integrity hash for the expected package artifact, and verify it before execution.
- Replace the mutable GitHub tree reference with an immutable, reviewed commit identifier or signed release artifact.
- Avoid using an ambiguous
npx addpackage invocation. Document an explicit installation mechanism whose package name, publisher, source, and purpose can be independently verified. - Recommend inspecting downloaded package contents before execution, for example by retrieving a pinned artifact without immediately invoking its CLI.
- Document the expected publisher identity and canonical repository so users can detect dependency confusion, typosquatting, or publisher changes.
- Execute installation in a minimally privileged environment without unnecessary credentials, secrets, or access to sensitive repositories.
- Keep the pinned version and integrity metadata synchronized in both
SKILL.mdandREADME.md.
- Replace
