T08 · Insecure Dependencies
- Location
SKILL.md:36- Finding
Unpinned Package Execution in Installation Instructions
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:36-39; duplicated inREADME.md:6-9
Vulnerability Type: Unpinned third-party package execution
Risk Level: MediumComplete vulnerable snippets:
SKILL.md:36-39:markdown ### 方法一:通过 ClawHub 安装 ```bash npx clawhub install smart-refinementtext `README.md:6-9`: ```markdown ## 快速安装 ```bash npx clawhub install smart-refinementtext ### Technical Analysis The documented installation command invokes `clawhub` through `npx` without specifying a reviewed package version or integrity value. If the package is not already available locally, `npx` may resolve and download the current package from the configured npm registry before executing its CLI code. Consequently, the code executed during installation can change after this Skill has been reviewed. The Skill itself has no runtime dependencies and its Python implementation contains no network or command-execution logic, so dynamically executing an unpinned installer introduces avoidable supply-chain exposure beyond the minimum privileges needed by the local prompt-refinement functionality. This finding does not establish that the current `clawhub` package is malicious. The vulnerability is the mutable and insufficiently verified dependency resolution process. ### Attack Path 1. An attacker compromises the registry account, publication pipeline, or upstream source associated with the resolved `clawhub` package. 2. The attacker publishes a malicious version under the package name resolved by `npx`. 3. A user follows the installation command from `SKILL.md` or `README.md`. 4. `npx` retrieves the mutable package version from the user's configured registry. 5. The downloaded CLI or applicable package lifecycle code executes with the privileges of the user running the installation command. 6. The malicious package can access resources available to that user before or while presenting ...[truncated 722 chars]- Remediation
View remediation
Remediation Suggestions
- Pin the installer to a specifically reviewed version:
bash npx clawhub@<reviewed-version> install smart-refinement - Document the expected registry and authoritative package publisher so users can detect registry substitution or similarly named packages.
- Publish and verify package integrity metadata or cryptographic signatures where supported.
- In controlled deployments, lock the resolved installer artifact in a package lockfile or internal artifact repository after security review.
- Prefer a platform-provided, already trusted installer over downloading and executing a mutable package at installation time.
- Advise users not to run the installation command with elevated privileges and to use a restricted environment with no unnecessary secrets.
- Apply the corrected command consistently in both
SKILL.mdandREADME.md.
- Pin the installer to a specifically reviewed version:
