T08 · Insecure Dependencies
- Location
README.md:41- Finding
Unpinned Package Execution Through npx
- Content
View full analysis
Vulnerability Details
File Location:
README.md:41-45
Vulnerability Type: Unpinned third-party package execution
Risk Level: MediumVulnerable Code
bash npx clawhub install ai-news-briefingTechnical Analysis
The documented installation procedure invokes
clawhubthroughnpxwithout specifying a reviewed package version or integrity value. If the package is not already available locally,npxcan retrieve the current package release from the configured npm registry and execute it with the invoking user's privileges.Consequently, the code executed by this command can change after this skill has been reviewed. Compromise of the package publisher, npm account, registry, or a future
clawhubrelease could turn the documented installation command into a supply-chain execution vector.No evidence establishes that the current
clawhubpackage is malicious. The vulnerability is the unsafe, unpinned trust relationship created by the documented command.Attack Path
- An attacker compromises the
clawhubpackage, its publisher account, its distribution infrastructure, or a future package release. - The attacker publishes a release containing malicious package code or lifecycle behavior.
- A user follows the installation command in
README.md. npxresolves and downloads the attacker-controlled current version because no version or integrity constraint is supplied.- The downloaded package executes under the user's account during installation.
- The payload can perform actions permitted to that user before or while installing the skill.
Impact Assessment
Successful exploitation could provide arbitrary code execution with the privileges of the user running the installation command. Depending on that user's permissions and environment, the payload could access user-readable files, environment variables, development credentials, project data, and network resources, or mod ...[truncated 305 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Pin
clawhubto a specific, reviewed version, for example:bash npx --yes clawhub@<reviewed-version> install ai-news-briefing - Verify the selected release's provenance and integrity before recommending it.
- Use a lockfile and registry-provided integrity metadata when installation is managed through a package manifest.
- Document the expected trusted registry and avoid silently accepting packages from alternate registry configurations.
- Prefer installing a verified CLI release separately and invoking the locally pinned binary rather than downloading and executing the latest release in one step.
- Review new versions before updating the pinned version and perform installation using a least-privileged account in an isolated environment.
- Pin
