T08 · Insecure Dependencies
- Location
README.md:17- Finding
Unpinned Package Execution in Installation Instructions
- Content
View full analysis
Vulnerability Details
File Locations:
README.md, lines 17-21README_CN.md, lines 17-21
Vulnerability Type: Unpinned third-party package execution
Risk Level: MediumVulnerable Code
README.md, lines 17-21:markdown ## Install ```bash npx clawhub install admapixtext `README_CN.md`, lines 17-21: ```markdown ## 安装 ```bash npx clawhub install admapixtext ### Technical Analysis The documented installation command invokes the npm-resolved `clawhub` package through `npx` without specifying an exact package version or verifying package integrity. If the package is not already present locally, `npx` can retrieve it from the configured npm registry and execute its package entry point. Because no version, checksum, signature, lockfile, or trusted artifact reference is provided, the code executed by this command can change independently of the reviewed Skill repository. This creates a supply-chain trust boundary: users are instructed to execute mutable third-party code that was not included in, and therefore could not be validated as part of, this audit. Exploitation would require compromise or malicious replacement of the upstream package, compromise of the configured package registry, or resolution of an unintended package. Interactive confirmation by some `npx` versions may reduce accidental execution but does not establish package authenticity. ### Attack Path 1. An attacker compromises the upstream `clawhub` npm package, its maintainer account, or a package registry used by the victim. 2. The attacker publishes a malicious version under the package name resolved by `npx`. 3. A user follows the installation instructions and runs: ```bash npx clawhub install admapixnpxresolves and downloads the mutable package version from the configured registry.- The downloaded package executes with the privileges of the user running the command.
- Malicious package code could access files available to that user ...[truncated 924 chars]
- Remediation
View remediation
Remediation Suggestions
-
Pin the installer to a specifically reviewed version:
bash npx clawhub@<audited-version> install admapix -
Publish the expected package version and trusted registry explicitly. Avoid relying on a user's potentially modified npm registry configuration.
-
Prefer a lockfile-backed installation workflow or a signed, versioned release artifact.
-
Publish cryptographic checksums or signatures for installer artifacts and document how users can verify them before execution.
-
Review the pinned installer version and its transitive dependencies before recommending it.
-
Advise users not to run the installation command with
sudoor from an administrator shell. -
Update both
README.mdandREADME_CN.mdso that all documented installation paths apply the same version pinning and verification controls.
-