T08 · Insecure Dependencies
- Location
README.md:5- Finding
Unpinned Package Execution Through a Mutable Release Tag
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 5–7
Vulnerability Type: Supply-chain risk caused by executing an unpinned third-party package
Risk Level: MediumVulnerable Code Snippet:
bash npx clawhub@latest install web-scraper-proTechnical Analysis
The documented installation command instructs users to execute
clawhubthroughnpxusing the mutablelatesttag. If the package is not already available locally,npxcan retrieve it from the configured package registry and execute it immediately.Because
latestdoes not identify an immutable, reviewed release, the code executed by this command may change after the skill has been audited. The repository provides no exact version pin, package integrity hash, lockfile, or other mechanism for verifying that users execute the same package version reviewed by the publisher.This creates a supply-chain exposure: compromise of the package publisher account, registry entry, release process, or mutable tag could cause the installation command to retrieve and run attacker-controlled code.
Attack Path
- An attacker compromises the
clawhubpackage publication process, its publisher account, or the corresponding registry entry. - The attacker publishes a malicious release and assigns it to the
latestdistribution tag. - A user follows the installation instructions in
README.md. npxretrieves the package version currently referenced bylatest.- The retrieved package executes with the privileges of the user who invoked the command.
- The malicious package can perform actions available to that user, such as reading accessible files, modifying user-owned data, making network requests, or installing additional user-level components.
Impact Assessment
Successful exploitation permits arbitrary code execution with the privileges of the user running the installation command. The affected scope may include that use ...[truncated 535 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
-
Replace the mutable
latesttag with an exact, reviewed package version, for example:bash npx clawhub@<reviewed-exact-version> install web-scraper-pro -
Publish and verify the expected package integrity digest or signature before execution.
-
Document the trusted package registry explicitly to reduce registry substitution or dependency-confusion risks.
-
Use a lockfile or equivalent immutable dependency manifest where installation tooling supports it.
-
Review each package update before changing the documented version, and use protected publishing credentials with multi-factor authentication.
-
Advise users not to run the installation command with administrator or root privileges unless strictly required.
-
