T08 · Insecure Dependencies
- Location
INSTALL.md:15- Finding
Unpinned and Inconsistent ClawHub CLI Package Execution
- Content
View full analysis
Vulnerability Details
File Location:
INSTALL.md:15-18
Vulnerability Type: Supply-chain exposure through an unpinned and inconsistent package reference
Risk Level: MediumVulnerable Code
markdown ### Method 2: Install from ClawHub (not yet published) ```bash npx clawhub@latest install xianyu-searchtext The package name conflicts with the scoped CLI identified in `PUBLISH.md:7-9`: ```markdown ```bash # 1. Install the ClawHub CLI npm install -g @openclaw/clawhubtext ### Technical Analysis The installation command instructs users to execute `clawhub@latest` through `npx`. This creates two related supply-chain risks: 1. The mutable `latest` tag does not pin the executable package to a reviewed version. 2. The unscoped package name `clawhub` differs from the documented scoped package `@openclaw/clawhub`. `npx` can retrieve and execute package code from the configured registry. Therefore, installation runs code that is not part of the audited project and whose effective contents may change after this project has been reviewed. If the unscoped package is unrelated, compromised, or controlled through package-name confusion, the command may execute attacker-controlled lifecycle or CLI code. This finding concerns the documented installation path. The audited project itself declares no runtime dependencies and its executable JavaScript does not fetch or execute remote code. ### Attack Path 1. A user follows the installation instructions in `INSTALL.md`. 2. The user runs: ```bash npx clawhub@latest install xianyu-search- The package manager resolves the mutable
latestrelease of the unscopedclawhubpackage from the configured registry. - Package lifecycle hooks or CLI entry-point code execute with the user's current privileges.
- If that package or release is malicious or compromised, it can perform arbitrary actions available to the user before or instead of installing the intended skill.
Impact Assessm
...[truncated 636 chars]
- The package manager resolves the mutable
- Remediation
View remediation
Remediation Suggestions
-
Use the verified scoped package consistently across all documentation:
bash npx --yes @openclaw/clawhub@<audited-version> install xianyu-search -
Replace
<audited-version>with an exact version rather than a mutable tag such aslatest. -
Confirm the package's official registry identity and ownership before publishing the command.
-
Keep
INSTALL.md,PUBLISH.md, and release documentation synchronized so they all reference the same package. -
Where possible, publish and verify package integrity metadata, signed releases, or checksums.
-
Advise users to run installation without elevated privileges and to review package provenance before execution.
-