T08 · Insecure Dependencies
- Location
README.md:6- Finding
Execution of an Unpinned Mutable Package Release
- Content
View full analysis
Vulnerability Details
File Location:
README.md, line 6
Vulnerability Type: Unpinned third-party package execution
Risk Level: MediumVulnerable Code Snippet:
bash npx clawhub@latest install qr-generatorTechnical Analysis
The documented installation command instructs users to download and execute the package version associated with the mutable
latestnpm distribution tag. The project does not pin an audited version or specify an integrity hash.Because the package selected by
latestcan change after this skill has been reviewed, the code ultimately executed by users is not fixed to the audited project state. If the upstream package, maintainer account, publishing process, or package registry is compromised, a malicious release can be assigned tolatestand executed throughnpx.This finding concerns the supply-chain trust boundary created by the installation instruction. The audited repository itself contains no embedded executable implementation or confirmed malicious payload.
Attack Path
- An attacker compromises the
clawhubpackage, its publisher credentials, or its release pipeline. - The attacker publishes a malicious package version and assigns it to the
latestdistribution tag. - A user follows the installation command in
README.md. npxresolves and downloads the attacker-controlled release.- Package lifecycle behavior or the invoked CLI executes with the privileges of the user running the command.
- The malicious release can access resources available to that user, subject to operating-system and runtime restrictions.
Impact Assessment
Successful exploitation could permit arbitrary code execution with the invoking user's privileges. Depending on those privileges and the host environment, affected resources could include user-accessible files, environment variables, credentials, network services, and project data. If the command is run by a p ...[truncated 128 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace the mutable
@latestreference with an exact, reviewed package version, for exampleclawhub@X.Y.Z. - Verify the selected release and document the expected package registry.
- Use lockfiles and registry-supported integrity hashes where applicable.
- Review package lifecycle scripts and transitive dependencies before recommending execution.
- Upgrade only through a controlled process that reviews and tests each new version before changing the documented pin.
- Avoid running package installation commands with administrative privileges.
- Replace the mutable
