T08 · Insecure Dependencies
- Location
README.md:34- Finding
Unpinned Third-Party Package Is Downloaded and Executed During Installation
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 34–38
Vulnerability Type: Mutable third-party dependency execution
Risk Level: MediumVulnerable Code
markdown ## Installation ```bash npx clawhub@latest install tetsuakira-vk/mandarin-daily-drilltext ### Technical Analysis The documented installation command invokes `npx` with the mutable `clawhub@latest` version specifier. If that package version is not already available locally, `npx` retrieves it from the configured package registry and executes its CLI code. The `latest` distribution tag can be changed after this skill has been reviewed, so the code ultimately executed by users is not fixed to the audited project state. This creates a supply-chain trust boundary: compromise of the upstream package, its publisher account, or the package registry could cause attacker-controlled code to execute when a user follows the installation instructions. No malicious package or payload is embedded in this repository; the risk arises from executing a mutable external dependency without version pinning or integrity verification. ### Attack Path 1. An attacker compromises the `clawhub` package publisher, release pipeline, or relevant registry account. 2. The attacker publishes a malicious package release and assigns it to the `latest` distribution tag. 3. A user follows the installation command in `README.md`. 4. `npx` downloads the attacker-controlled release selected by `clawhub@latest`. 5. Package lifecycle behavior or CLI initialization code executes with the privileges of the user running the command. 6. The malicious package may access or modify resources available to that user before or while processing the requested skill installation. ### Impact Assessment Successful exploitation could provide arbitrary code execution with the privileges of the installing user. Depending on the user's permissions and environment, the affected scop ...[truncated 563 chars]- Remediation
View remediation
Remediation Suggestions
- Replace
clawhub@latestwith an explicitly pinned, reviewed version, for example:bash npx clawhub@<reviewed-version> install tetsuakira-vk/mandarin-daily-drill - Update the pinned version only after reviewing the release provenance, changelog, and package contents.
- Use package-manager integrity verification, a lockfile, or a verified package hash where the installation workflow supports it.
- Document the expected package registry and warn users against installing from untrusted registry mirrors.
- Prefer a trusted, signed release mechanism and verify publisher provenance or package signatures where available.
- Recommend installation from a non-privileged account and avoid running the command with administrator or root permissions.
- In CI/CD environments, restrict network access and credentials available to the installation process to limit the impact of an upstream compromise.
- Replace
