T08 · Insecure Dependencies
- Location
README.md:27- Finding
Unpinned Executable Installer Creates a Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Locations:
README.md:25-30README.zh-CN.md:25-30docs/INSTALL.md:10-16docs/INSTALL.md:34-39docs/INSTALL.zh-CN.md:10-16docs/INSTALL.zh-CN.md:34-39
Vulnerability Type: T08: Insecure Dependencies
Risk Level: MediumVulnerable Code Snippets
README.md:25-30:bash # One-command install (both platforms) npx clawhub@latest install 0xcjl/anti-sycophancy # Or via Claude Code /anti-sycophancy installdocs/INSTALL.md:10-16:markdown ## Method 1: Via ClawhHub (Recommended) ```bash npx clawhub@latest install 0xcjl/anti-sycophancyThis automatically installs all applicable layers for your detected platform.
text `docs/INSTALL.md:34-39`: ```markdown ## Method 3: Via ClawhHub + Claude Code combination ```bash # Install via ClawhHub npx clawhub@latest install 0xcjl/anti-sycophancyTechnical Analysis
The recommended installation command asks
npxto resolve, download, and execute the mutablelatestrelease of the third-partyclawhubpackage. Because no exact version or package-integrity value is specified, the code executed during installation is not necessarily the code that existed when this Skill was audited.If the package publisher account, package registry, release process, or the current
latestrelease is compromised, users following the documented instructions could execute a malicious package. The audited repository itself contains no malicious dependency or payload, but the installation process crosses an unpinned supply-chain trust boundary.The same command is repeated in the corresponding Chinese documentation at the listed locations, so users of either documentation set are exposed to the same risk.
Attack Path
- An attacker compromises the
clawhubpackage publisher, registry entry, release pipeline, or another mechanism capable of changing the version identified by ...[truncated 1282 chars]
- Remediation
View remediation
Remediation Suggestions
-
Replace
clawhub@latestwith an exact, reviewed version:bash npx --yes --package=clawhub@1.0.0 clawhub install 0xcjl/anti-sycophancyThe example version should be replaced with a release that the maintainers have explicitly audited.
-
Update every English and Chinese installation example consistently so no documentation path continues recommending
@latest. -
Publish expected package provenance, checksums, or registry integrity information and explain how users can verify it before execution.
-
Prefer a lockfile-backed installation workflow where supported, and enable package-manager signature or provenance verification.
-
Recommend running installation without administrative privileges and in a restricted environment with access only to the files required for installation.
-
Establish a controlled upgrade process in which new
clawhubreleases are reviewed and the documented pinned version is updated only after verification.
-
