T08 · Insecure Dependencies
- Location
SKILL.md:19- Finding
Unpinned Package Execution Through npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 19–25
Vulnerability Type: Unpinned third-party package execution
Risk Level: MediumVulnerable Code
yaml metadata: category: skills tagline: >- Turn fresh-cut branches into heirloom-quality spoons and utensils that last decades — agent owns the species math and schedules so you stay in the knife work and grain reading. display_name: "Green Wood Spoon Carving Basics" submitted_by: HowToUseHumans last_reviewed: "2026-03-31" openclaw: requires: tools: [filesystem] install: "npx clawhub install green-wood-spoon-carving-basics"The same unpinned installation command is repeated in the document body:
text npx clawhub install green-wood-spoon-carving-basicsTechnical Analysis
The installation instructions invoke
clawhubthroughnpxwithout specifying an audited package version or integrity digest. Depending on the local npm configuration and cache state,npxcan download the current registry version of the package and execute its code. The effective code executed by this command can therefore change after the skill has been audited.The target skill name is also not version-pinned in the installation command. No lockfile, package integrity hash, trusted source declaration, or signature-verification procedure is provided. Consequently, compromise of the relevant registry account, package namespace, distribution infrastructure, or a future package release could introduce code not represented in this repository.
Attack Path
- An attacker compromises the publishing account, registry package, package namespace, or release process associated with
clawhubor the requested skill. - The attacker publishes a malicious or modified release under the expected package name.
- A user follows the documented
npx clawhub install green-wood-spoon-carving-basicsinstruction. npx...[truncated 950 chars]
- An attacker compromises the publishing account, registry package, package namespace, or release process associated with
- Remediation
View remediation
Remediation Suggestions
- Pin the CLI to a specifically reviewed version, for example
npx clawhub@<audited-version> ..., rather than resolving the latest available release. - Pin the installed skill to an immutable version or content digest if the installer supports it.
- Use a lockfile and verify registry-provided integrity hashes before execution.
- Document the expected official registry and source repository to reduce dependency-confusion and namespace-substitution risks.
- Prefer a preinstalled, organization-approved CLI instead of implicitly downloading and executing a package during installation.
- Verify package signatures or provenance attestations where supported.
- Run installation with least privilege in a restricted environment, without unnecessary secrets or sensitive environment variables.
- Disable or audit dependency lifecycle scripts where operationally possible.
- Pin the CLI to a specifically reviewed version, for example
