T08 · Insecure Dependencies
- Location
README.md:16- Finding
Unpinned Package Execution in Installation Instructions
- Content
View full analysis
Vulnerability Details
File Location:
README.md, line 16
Vulnerability Type: Supply-chain risk caused by executing an unpinned package
Risk Level: MediumVulnerable Code
bash npx clawhub install maxhub-threadsTechnical Analysis
The documented installation command invokes
clawhubthroughnpxwithout specifying a package version or integrity constraint. If the package is not already available locally,npxmay retrieve and execute the package version currently published by the configured registry.Consequently, the code executed during installation is mutable and is not necessarily the same code that existed when this Skill was audited. Compromise of the package publisher, registry account, package release process, or transitive dependency chain could turn the installation command into a code-execution vector.
The same command is duplicated in
README_CN.mdat line 16. That duplicate does not create an independent vulnerability and is covered by this finding.Attack Path
- An attacker compromises the
clawhubpackage, its publisher account, release pipeline, registry distribution path, or a dependency executed by the package. - The attacker publishes a malicious version under the expected package name.
- A user follows the installation documentation and runs
npx clawhub install maxhub-threads. npxresolves and retrieves the mutable package version from the configured registry.- The malicious package executes with the operating-system privileges of the user running the command.
This is a supply-chain attack path; the audited repository itself does not contain evidence of an active malicious package or embedded payload.
Impact Assessment
Successful exploitation could permit arbitrary code execution under the installing user's account. The resulting scope could include access to files, environment variables, credentials, network resources, and configuration available to that account. Additional sy ...[truncated 129 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
-
Pin the installer to a specifically reviewed version, for example:
bash npx clawhub@<reviewed-version> install maxhub-threads -
Publish and verify package integrity information or signatures before execution.
-
Document the expected package registry and discourage installation from untrusted registry mirrors.
-
Prefer a previously installed and independently verified CLI over implicit download-and-execute behavior.
-
Use lockfiles or equivalent dependency controls wherever the installation workflow supports them.
-
Apply the same hardened command to both
README.mdandREADME_CN.md. -
Advise users not to run the installation command with administrative privileges unless strictly required.
-
