T08 · Insecure Dependencies
- Location
SKILL.md:10- Finding
Unpinned Package Execution Through npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 10
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumComplete Code Snippet:
yaml install: "npx clawhub install village-carpenter-starter"Technical Analysis
The installation command invokes
npxwithout specifying an exact version of theclawhubpackage or an integrity value. Depending on the local environment and package cache,npxcan download and execute the version currently published under that package name.This makes the effective installer mutable after the skill has been reviewed. If the package registry account, package, release pipeline, or configured registry is compromised, a malicious package version could execute during installation. The project does not provide a lockfile, checksum, package provenance requirement, or other mechanism for verifying the downloaded executable.
Attack Path
- An attacker compromises the package, its publishing credentials, its release pipeline, or the package source configured for the victim.
- The attacker publishes a malicious version under the package name resolved by
npx. - A user runs the documented installation command.
npxresolves and downloads the unpinned package version.- Malicious package or lifecycle code executes with the privileges of the user running the command.
Impact Assessment
Successful exploitation could allow arbitrary code execution under the installing user's account. The accessible scope may include files, environment variables, credentials available to that account, and network resources reachable from the host. Administrative impact would require the command to be run from an elevated account or an additional privilege-escalation mechanism.
- Remediation
View remediation
Remediation Suggestions
- Pin the installer to an exact, reviewed version, such as
clawhub@<exact-version>. - Verify the resolved package using a trusted lockfile or documented integrity hash.
- Configure and document the expected package registry rather than relying on ambient registry configuration.
- Review package provenance and signatures where the package ecosystem supports them.
- Prefer installing an audited version separately and invoking the local executable without allowing automatic retrieval of a newer release.
- Run installation with a non-privileged account and in a restricted environment.
- Pin the installer to an exact, reviewed version, such as
