T08 · Insecure Dependencies
- Location
SKILL.md:30- Finding
Unpinned Third-Party Installation and Unscoped Dependency Updates
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 30–34
Vulnerability Type: Supply-chain risk from mutable third-party dependencies
Risk Level: MediumVulnerable Code
bash npx -y clawhub@latest install deepresearchwork npx -y clawhub@latest install tavily-search npx -y clawhub@latest install literature-search npx -y clawhub@latest install perplexity-deep-search npx -y clawhub@latest update --allTechnical Analysis
The installation procedure invokes the mutable
clawhub@latestnpm package and installs Skill releases without pinning them to the versions that were inspected. It also runsupdate --all, which can update unrelated installed Skills outside this project's dependency scope.Consequently, the code executed during installation is not necessarily the code previously reviewed. If the npm package, registry account, distribution channel, or an upstream Skill release is compromised or changed, following these instructions may retrieve and execute an unreviewed payload with the invoking user's privileges.
Attack Path
- An attacker compromises the
clawhubnpm package, an upstream Skill publisher account, or the relevant package-distribution channel. - The attacker publishes a malicious release under the mutable
latestreference or replaces an unpinned upstream Skill release. - A user follows the documented installation or update procedure.
npxdownloads and executes the changedclawhub@latestpackage.- The installer retrieves the malicious Skill release, or
update --allupdates another installed Skill to a compromised version. - The malicious dependency executes under the user's account when installed or subsequently invoked.
Impact Assessment
Successful exploitation could provide arbitrary code execution with the privileges of the user running the commands. Depending on that user's access, the payload could read local files and environment variables—including declared API credentials—modi ...[truncated 300 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Pin the
clawhubCLI to a specific reviewed version rather than using@latest. - Pin each upstream Skill to its reviewed version:
deepresearchworkversion1.0.0tavily-searchversion1.0.0literature-searchversion1.0.3perplexity-deep-searchversion1.0.0
- Record and verify cryptographic integrity hashes or trusted publisher signatures before installation.
- Remove
npx -ywhere practical so unexpected package retrieval does not proceed without review. - Replace
update --allwith explicit, individually versioned updates limited to required dependencies. - Review release diffs and repeat the security audit before changing pinned versions.
- Run installation and Skill execution in a least-privileged, isolated environment with access only to required files and credentials.
- Restrict API credentials to the minimum required permissions and avoid exposing unrelated secrets to dependency processes.
- Pin the
