T08 · Insecure Dependencies
- Location
SKILL.md:15- Finding
Unpinned Package Execution Through npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 15–22
Vulnerability Type: Unpinned third-party package execution
Risk Level: MediumVulnerable Code
yaml openclaw: requires: tools: [filesystem] install: "npx clawhub install pine-pitch-glue-making-basics" --- # Pine Pitch Glue Making Basics `npx clawhub install pine-pitch-glue-making-basics`Technical Analysis
The documented installation procedure executes
clawhubthroughnpxwithout specifying an audited package version, lockfile, package integrity hash, or trusted registry. If the package is not already available locally,npxcan retrieve and execute the version currently resolved by the configured npm registry.Consequently, the executable used at installation time may differ from the version that was originally reviewed. This creates a supply-chain trust boundary in which compromise of the package, its publishing account, the configured registry, or a future package release could result in attacker-controlled code being executed.
The same unpinned command appears both in the installation metadata and in the user-facing instructions, making it the expected installation path rather than an incidental example.
Attack Path
- An attacker compromises the
clawhubpackage, its publisher account, its dependency chain, or the registry through which it is resolved. - The attacker publishes a malicious version that still provides the expected CLI command.
- A user follows the documented
npx clawhub install pine-pitch-glue-making-basicsinstruction. npxresolves and downloads the attacker-controlled or otherwise unreviewed package version.- The malicious package executes with the privileges and environment of the user running the installation command.
- The payload may access files available to that user, alter installed skill content, read exposed environment variables, or execute additional comma ...[truncated 761 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Pin the installer to a specific, reviewed version, for example:
sh npx --yes clawhub@<audited-version> install pine-pitch-glue-making-basics - Verify the package against an expected cryptographic integrity value or signed provenance before execution.
- Use a lockfile and a controlled registry or internal package mirror to ensure deterministic resolution.
- Review the pinned package and its transitive dependencies before approving installation.
- Execute installation in a sandbox or least-privileged environment without unnecessary credentials, sensitive environment variables, or writable access to unrelated files.
- Update both the metadata installation command and the user-facing command so they reference the same verified version.
- Establish a controlled update process in which newer versions are reviewed and their pins and integrity metadata are updated explicitly rather than resolving the latest release automatically.
- Pin the installer to a specific, reviewed version, for example:
