T08 · Insecure Dependencies
- Location
SKILL.md:25- Finding
Unpinned Package Execution in Installation Instructions
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 25
Vulnerability Type: Supply-chain risk caused by execution of a mutable package release
Risk Level: MediumVulnerable Code Snippet:
bash npx clawhub@latest install ai-freelance-helperTechnical Analysis
The documented installation command instructs users to execute the
latestrelease of theclawhubnpm package. Thelatestdistribution tag is mutable and does not identify a specific, previously audited artifact. The project also provides no lockfile, package integrity hash, or other mechanism that constrains the installer to a known release.npxcan download and execute package-provided code. Consequently, the code executed by this command may differ from the code that existed when the skill was audited. This creates a supply-chain trust boundary outside the reviewed project.This finding does not establish that the current
clawhubpackage is malicious. The vulnerability is the unsafe reliance on an unpinned, externally controlled executable package version.Attack Path
- An attacker compromises the upstream npm package, a maintainer account, the package publication workflow, or another component of the relevant distribution chain.
- The attacker publishes a modified release and assigns it to the mutable
latestdistribution tag. - A user follows the installation instructions in
SKILL.md. npxresolvesclawhub@latest, downloads the attacker-controlled release, and executes its package entry point or lifecycle behavior.- The malicious package performs actions with the permissions of the user running the command.
Impact Assessment
Successful exploitation can provide arbitrary code execution under the installing user's account. Depending on that user's permissions and environment, an attacker could read or modify user-accessible files, access environment variables and development credentials, alter the ...[truncated 342 chars]
- Remediation
View remediation
Remediation Suggestions
-
Replace the mutable
latesttag with an exact, reviewed package version, for example:bash npx clawhub@X.Y.Z install ai-freelance-helper -
Verify the selected package release and its provenance before recommending it.
-
Where supported, validate the downloaded artifact against a published integrity hash or signed release.
-
Use a trusted, explicitly configured package registry and protect package publication accounts with strong authentication and restricted release permissions.
-
Establish an update process in which new installer versions are reviewed and tested before the pinned version in the documentation is changed.
-
Advise users not to execute the installer with elevated privileges unless they have independently verified the package and elevation is strictly necessary.
-
