T08 · Insecure Dependencies
- Location
README.md:14- Finding
Unpinned Package Execution in Installation Instructions
- Content
View full analysis
Vulnerability Details
File Location:
README.md:14-18andREADME_CN.md:14-18
Vulnerability Type: Unpinned third-party package execution
Risk Level: MediumVulnerable Code
README.md:14-18:markdown ## Install ```bash npx clawhub install maxhub-lemon8text `README_CN.md:14-18`: ```markdown ## 安装 ```bash npx clawhub install maxhub-lemon8text ### Technical Analysis The documented installation command uses `npx` to resolve and execute the `clawhub` package without specifying an exact package version or verifying its integrity. When the package is not already available locally, `npx` may retrieve executable package content from the configured npm registry. The effective code executed during installation can therefore change after this Skill has been reviewed. The repository contains no lock file, integrity hash, vendored installer, or other mechanism that constrains which version of the external package will run. This creates a supply-chain exposure. If the package, publisher account, package registry, dependency tree, or local npm registry configuration is compromised, the command could execute code that was not included in this audit. The audited Skill itself does not contain evidence that the referenced package is malicious; the vulnerability is the absence of version and integrity controls around executable dependency retrieval. ### Attack Path 1. An attacker compromises the `clawhub` package, one of its executable dependencies, its publisher account, or the registry from which it is resolved. 2. Alternatively, an attacker influences the victim's npm configuration so that `npx` resolves the package through an untrusted registry. 3. The victim follows the README and runs: ```bash npx clawhub install maxhub-lemon8 ``` 4. `npx` retrieves the currently resolved package rather than a version whose content was fixed at audit time. 5. Package initializat ...[truncated 1051 chars]- Remediation
View remediation
Remediation Suggestions
-
Pin the installer to a specifically reviewed version:
bash npx --yes clawhub@<audited-version> install maxhub-lemon8 -
Document the expected npm registry explicitly and advise users to verify their registry configuration before installation:
bash npm config get registry -
Publish and document a cryptographic integrity value or signed release provenance for the installer package. Verify that value before executing downloaded content.
-
Prefer a lockfile-backed installation workflow where practical, ensuring that both direct and transitive dependency versions are fixed.
-
Avoid recommending installation from an elevated shell. State that the installer should run with ordinary user privileges and only the filesystem permissions required to install the Skill.
-
For higher-assurance deployments, download the pinned package without executing it, inspect or verify its contents, and only then invoke the verified local artifact.
-
Apply the corrected, pinned command consistently in both
README.mdandREADME_CN.md.
-