T08 · Insecure Dependencies
- Location
SKILL.md:33- Finding
Unpinned npm Installer Executes a Mutable Registry Package
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:19,SKILL.md:33, andREADME.md:21
Vulnerability Type: Unpinned third-party installer dependency
Risk Level: MediumVulnerable Code
SKILL.md:19:markdown - Recommended install path: ClawHub registry (`npx clawhub@latest install clawtributor`)SKILL.md:33:bash npx clawhub@latest install clawtributorREADME.md:21:bash npx clawhub@latest install clawtributorTechnical Analysis
The recommended installation command asks
npxto resolve and execute the package currently referenced by the mutablelatestdistribution tag. It neither pins the installer to an exact reviewed version nor specifies an integrity value.Although
SKILL.mdseparately documents signature, public-key fingerprint, and SHA-256 verification for standalone release artifacts, those checks do not authenticate the npm package executed by the primary registry installation path. Consequently, the code that runs during installation can differ from the code that was originally reviewed.This creates a supply-chain trust boundary in which compromise of the npm publisher account, registry package, distribution tag, or installer dependency graph could cause users to execute substituted code.
Attack Path
- An attacker compromises the
clawhubnpm publisher account, package, release process, or a dependency used by the installer. - The attacker publishes a malicious package version and points the mutable
latesttag to it. - A user or Agent follows the documented
npx clawhub@latest install clawtributorinstruction. npxdownloads and executes the attacker-controlled package.- The malicious package performs actions using the privileges and accessible resources of the account that invoked the command.
Impact Assessment
Successful exploitation could grant attacker-controlled code the effective privileges of the invoking user. Depending on the local environment, this may per ...[truncated 351 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
clawhub@latestwith an exact, reviewed installer version. - Document the expected package integrity hash and require integrity verification before execution where supported.
- Pin or lock the installer dependency graph and protect publication with strong account controls, provenance attestations, and reproducible builds.
- Extend the existing signed-release verification model to the primary registry installation path so the installed Skill version and installer are authenticated.
- Prefer downloading a verified artifact before running any installer logic, rather than allowing
npxto resolve and immediately execute mutable content. - Keep the existing public-key fingerprint, signature, and checksum checks for standalone releases, and clearly state that they do not validate the npm installer itself.
- Apply the corrected command consistently at
SKILL.md:19,SKILL.md:33, andREADME.md:21.
- Replace
