T08 · Insecure Dependencies
- Location
README.md:4- Finding
Unpinned Package Execution in Installation Instructions
- Content
View full analysis
Vulnerability Details
File Location:
README.md, line 4
Vulnerability Type: Unpinned third-party package execution
Risk Level: MediumVulnerable Code
bash npx clawhub install SLUGTechnical Analysis
The documented installation command invokes
clawhubthroughnpxwithout specifying a package version, integrity hash, lockfile, or trusted distribution source. If the package is not already available locally,npxmay resolve, download, and execute the current package release from the configured npm registry.This creates a supply-chain trust dependency on the package name, registry configuration, publisher account, and latest available release. A compromised publisher account, malicious package update, registry substitution, or dependency-confusion condition could cause code that was never reviewed with this project to execute during installation.
The repository does not contain evidence that the resolved package is presently malicious. The vulnerability is the unsafe installation pattern and its lack of reproducibility or integrity controls.
Attack Path
- An attacker compromises the publishing account or distribution channel for the package resolved as
clawhub, or causes the victim's registry configuration to resolve an attacker-controlled package. - The attacker publishes a release containing malicious package initialization or lifecycle behavior.
- A user follows the installation command from
README.md. npxresolves and downloads the unpinned package release.- The downloaded package executes with the privileges of the user running the command.
- Malicious package code can access resources available to that user before or while processing the requested Skill installation.
Impact Assessment
Successful exploitation can provide arbitrary code execution under the installing user's account. The reachable scope may include user-readable files, environment variabl ...[truncated 415 chars]
- An attacker compromises the publishing account or distribution channel for the package resolved as
- Remediation
View remediation
Remediation Suggestions
- Pin
clawhubto a reviewed, immutable version rather than implicitly executing the latest release. - Document the expected official registry and package publisher.
- Verify package integrity through a lockfile, checksum, signature, or equivalent provenance control.
- Prefer installing the reviewed package version separately and then invoking the locally installed executable.
- Disable or carefully review package lifecycle scripts where supported.
- In CI environments, execute installation with a minimally privileged account and without unrelated credentials in the environment.
- Add an upgrade process that reviews package changes before updating the pinned version.
- Pin
