T08 · Insecure Dependencies
- Location
SKILL.md:15- Finding
Unpinned Package Execution Through npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 15
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumVulnerable Code:
yaml openclaw: requires: tools: [filesystem] install: "npx clawhub install pet-first-aid"Technical Analysis
The installation command invokes
clawhubthroughnpxwithout specifying an exact package version or integrity constraint. Depending on the local npm environment,npxmay retrieve the current package release from the configured package registry and execute it. The project contains no lockfile, checksum, vendored installer, or other mechanism that establishes whichclawhubartifact was reviewed and trusted.This creates a mutable supply-chain boundary: the code executed during installation may differ from the code available when the Skill was audited. Exploitation would require compromise or malicious control of the package, package publisher, registry resolution, or configured registry.
Attack Path
- An attacker compromises the package publisher, takes over the package, influences dependency resolution, or controls a registry configured on the victim's system.
- The attacker publishes or serves a malicious version of
clawhub. - A user follows the declared installation procedure.
npxresolves and downloads the unpinned package version.- Malicious package code or lifecycle behavior executes with the privileges of the user running the command.
Impact Assessment
Successful exploitation could provide arbitrary code execution under the installing user's account. The resulting access could include reading or modifying files available to that user, accessing environment variables and local credentials, making network requests, and altering the installed Skill. Administrative impact would occur only if the user executes the installation command with elevated privileges; no automatic privilege elevation is shown ...[truncated 20 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
clawhubto an exact, reviewed version, for example by using an explicit version rather than an unconstrained package name. - Record and verify the expected package integrity hash.
- Use a lockfile or equivalent reproducible dependency manifest where supported.
- Configure installation to use a trusted registry and document the expected package publisher.
- Disable or carefully review dependency lifecycle scripts where the installation workflow permits it.
- Periodically audit the pinned release and update it through a controlled review process.
- Pin
