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 and 20
Vulnerability Type: Unpinned third-party package execution
Risk Level: MediumVulnerable Code
yaml openclaw: requires: tools: [filesystem] install: "npx clawhub install besom-broom-making-basics"bash npx clawhub install besom-broom-making-basicsTechnical Analysis
The documented installation process invokes the
clawhubnpm package throughnpxwithout specifying a fixed package version or integrity value. Consequently, the code resolved from the package registry at installation time may differ from the version originally reviewed.An npm package can contain executable entry points and lifecycle scripts. If the upstream package, maintainer account, package registry, or dependency chain is compromised, following this command could execute attacker-controlled code. The project contains no lockfile, vendored installer, checksum, signature, or other mechanism for verifying the resolved package.
This finding concerns the mutable
clawhubinstaller dependency. The audit found no evidence that the broom-making Skill itself contains an embedded malicious payload.Attack Path
- An attacker compromises the
clawhubpackage, one of its transitive dependencies, its publisher account, or the package distribution channel. - The attacker publishes a malicious package release or replaces an expected dependency with attacker-controlled content.
- A user follows the installation instruction and runs:
bash npx clawhub install besom-broom-making-basics npxresolves and downloads the mutable package version available through the configured npm registry.- The malicious package entry point or lifecycle behavior executes with the privileges of the user running the command.
- The payload can access resources available to that user, subject to operating-system controls and the execu ...[truncated 654 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Pin the installer to a specific reviewed version, for example:
bash npx --yes clawhub@<reviewed-version> install besom-broom-making-basics - Verify the selected package version and its transitive dependency tree before publishing the installation command.
- Use a lockfile or equivalent immutable dependency manifest where the installation workflow supports one.
- Validate package integrity through registry integrity metadata, trusted signatures, or independently published checksums.
- Configure an explicitly trusted npm registry rather than relying on an uncontrolled registry configuration.
- Disable or tightly control npm lifecycle scripts where they are not required.
- Run installation in a sandbox or least-privileged environment without sensitive credentials.
- Document the exact reviewed installer version and establish a controlled process for reviewing and updating it.
- Pin the installer to a specific reviewed version, for example:
