T08 · Insecure Dependencies
- Location
README.md:37- Finding
Unpinned Package Execution Through npx
- Content
View full analysis
Vulnerability Details
File Location:
README.md, line 37
Vulnerability Type: Execution of a mutable third-party package release
Risk Level: Mediumbash npx clawhub@latest install tetsuakira-vk/french-daily-drillTechnical Analysis
The documented installation command instructs users to download and execute the package currently associated with the mutable
latesttag. Because no reviewed version or integrity value is specified, the code executed bynpxcan change after this project has been audited.This creates a supply-chain trust boundary outside the reviewed project. If the package registry, publisher account, package, or release process is compromised, an attacker could publish a malicious version under
latest. A user following the documentation would then download and execute that version without an opportunity to compare it against a known-good release.The command also installs the skill by a mutable repository identifier rather than an explicitly reviewed version, commit, or artifact digest. The audited project itself contains no malicious scripts; the risk arises from the unpinned installation path documented in the README.
Attack Path
- An attacker compromises the
clawhubpackage, its publisher account, or the relevant package-distribution infrastructure. - The attacker publishes a malicious package release and assigns it the
latestdistribution tag. - A user follows the installation instructions and runs
npx clawhub@latest install tetsuakira-vk/french-daily-drill. npxretrieves and executes the attacker-controlled package in the user's environment.- The malicious package performs actions with the permissions of the invoking user, such as reading accessible files, stealing environment credentials, modifying user configuration, or installing additional payloads.
Exploitation depends on compromise or malicious control of the external distribution channel; no dir ...[truncated 611 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
clawhub@latestwith a specific, reviewed version, for exampleclawhub@X.Y.Z. - Pin the installed skill to a version, immutable commit, or content digest if the installer supports it.
- Publish expected integrity hashes or signature-verification instructions for release artifacts.
- Document the expected package registry and avoid silently accepting packages from alternate or user-controlled registries.
- Review the pinned CLI and skill release before updating either version.
- Use lockfiles or equivalent dependency-integrity controls where supported.
- Recommend running installation without administrative privileges and in an isolated environment when practical.
- Replace
