T08 · Insecure Dependencies
- Location
README.md:14- Finding
Unpinned npm CLI Package Is Downloaded and Executed During Installation
- Content
View full analysis
Vulnerability Details
File Location:
README.md:14andREADME_CN.md:14
Vulnerability Type: Supply-chain risk from unpinned third-party package execution
Risk Level: MediumVulnerable Code
README.md:13-15:bash npx clawhub install maxhub-toutiaoREADME_CN.md:13-15:bash npx clawhub install maxhub-toutiaoTechnical Analysis
Both installation guides instruct users to execute the
clawhubnpm package throughnpxwithout specifying a reviewed version or integrity constraint. If the package is not available locally,npxcan retrieve it from the configured npm registry and immediately execute its CLI.Because package resolution is mutable, the code executed by this command may differ from the code that existed when the Skill was audited. The project does not provide a package version, cryptographic digest, signature-verification procedure, or other mechanism that binds installation to a reviewed artifact.
This is an insecure dependency and remote execution channel at installation time. It does not establish that the current
clawhubpackage is malicious, but it makes users dependent on the continuing integrity of the package publisher, npm account, registry, network path, and local npm configuration.Attack Path
- An attacker compromises the
clawhubnpm publisher account, package distribution process, or another relevant package-resolution component. - The attacker publishes a malicious or compromised version under the package name resolved by
npx. - A user follows either README and runs
npx clawhub install maxhub-toutiao. npxretrieves the currently resolved package because the documentation does not pin a reviewed version.- The downloaded package's CLI code executes with the privileges of the user running the installation command.
- Malicious code can perform actions permitted to that user before, during, or instead of installing the Skill. ...[truncated 687 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
-
Pin the installer to a specifically reviewed package version in both README files:
bash npx --yes clawhub@<reviewed-version> install maxhub-toutiao -
Confirm and document the authoritative npm package name, publisher, and official registry source so users can detect dependency-confusion or package-spoofing attempts.
-
Publish a checksum, signed release, or other verifiable provenance information for the reviewed installer artifact.
-
Recommend reviewing the resolved version before execution, especially in CI/CD or privileged environments.
-
Keep the English and Chinese installation instructions synchronized so neither document retains the unpinned command.
-
Avoid running the installer as root or another privileged account, and use an isolated environment where practical.
-
