T08 · Insecure Dependencies
- Location
README.md:5- Finding
Mutable Package Version Executed During Installation
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 5-7
Vulnerability Type: Unpinned third-party package execution
Risk Level: Mediumbash npx clawhub@latest install blood-sugar-trackerTechnical Analysis
The documented installation procedure invokes
npxwith the mutablelatesttag. If the package is not already available locally,npxretrieves it from the configured npm registry and executes its command-line entry point. The package may also run lifecycle scripts during installation.Because
latestcan be reassigned to a different release at any time, the code executed by this command is not fixed to the version that was reviewed when the documentation was published. No exact version, lockfile, integrity digest, or provenance-verification procedure is supplied. Consequently, compromise of the package publisher, registry account, or a future release could turn this documented installation command into a supply-chain execution vector.Attack Path
- An attacker compromises the
clawhubpackage publisher account, publishing pipeline, or relevant registry distribution channel. - The attacker publishes a malicious release and assigns the mutable
latesttag to it. - A user follows the installation command from
README.md. npxdownloads the attacker-controlled package release.- Malicious lifecycle scripts or the package's command-line entry point execute under the user's account.
- The payload can access resources available to that user and can modify files or invoke additional programs within the user's permission boundaries.
Impact Assessment
Successful exploitation permits arbitrary code execution with the privileges of the user running the documented command. Potential impact includes theft of user-accessible credentials and files, modification of local project or configuration data, execution of additional payloads, and compromise of development environments. T ...[truncated 236 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace the mutable
latesttag with an exact, reviewed version, for example:bash npx clawhub@1.2.3 install blood-sugar-tracker - Review the selected release, including its command-line entry point, transitive dependencies, and npm lifecycle scripts, before recommending it.
- Prefer installing the tool as a pinned project dependency and committing the applicable lockfile so dependency versions and integrity values are reproducible.
- Configure and document the expected trusted npm registry rather than relying on an arbitrary user-level registry configuration.
- Verify package provenance, signatures, and published integrity metadata where supported.
- Establish an update process in which the pinned version is changed only after the new release has undergone security review.
- Advise users not to execute the installation command with elevated privileges.
- Replace the mutable
