T08 · Insecure Dependencies
- Location
SKILL.md:15- Finding
Unpinned Third-Party Package Execution Through npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 15–22
Vulnerability Type:T08: Insecure Dependencies
Risk Level: MediumVulnerable Code
yaml openclaw: requires: tools: [filesystem] install: "npx clawhub install deliberate-practice-for-manual-skills"shell npx clawhub install deliberate-practice-for-manual-skillsTechnical Analysis
The documented installation command invokes
clawhubthroughnpxwithout specifying an exact package version or integrity value. If the package is not already available locally,npxcan retrieve it from the configured package registry and execute it with the permissions of the invoking user.Because neither a version constraint nor a cryptographic checksum is supplied, the executable selected when the command is run may differ from the version that existed when this Skill was reviewed. The repository contains only
SKILL.md; it does not include the retrieved package, a lockfile, or other information that would permit auditing the package implementation or its installation-time behavior.This is a supply-chain trust issue rather than evidence that the current
clawhubpackage is malicious. Exploitation depends on compromise or unauthorized modification of the package, its registry account, the configured package registry, or another relevant dependency-resolution mechanism.Attack Path
- An attacker compromises the package publication account, registry entry, distribution channel, or another dependency-resolution component used for
clawhub. - The attacker publishes a modified package version containing malicious installation-time or runtime behavior.
- A user follows the instruction
npx clawhub install deliberate-practice-for-manual-skills. npxresolves and downloads the mutable package version from the configured registry.- The downloaded package executes under the invoking user's account.
- The malic ...[truncated 856 chars]
- An attacker compromises the package publication account, registry entry, distribution channel, or another dependency-resolution component used for
- Remediation
View remediation
Remediation Suggestions
- Pin
clawhubto a reviewed exact version, for example:shell npx --yes clawhub@<reviewed-exact-version> install deliberate-practice-for-manual-skills - Verify the package archive against a trusted cryptographic digest or signed provenance record before execution.
- Document the expected registry explicitly and enforce a trusted registry configuration to reduce dependency-confusion and registry-redirection risks.
- Use a lockfile or an equivalent immutable dependency manifest covering the installer and its transitive dependencies.
- Review package lifecycle scripts and disable unnecessary installation scripts where the package manager supports doing so.
- Run installation in a sandbox or least-privileged environment without sensitive credentials, broad filesystem access, or administrative permissions.
- Prefer distributing an audited, versioned installer artifact with reproducible-build or provenance metadata rather than dynamically executing the latest registry release.
- Pin
