T08 · Insecure Dependencies
- Location
SKILL.md:14- Finding
Unpinned ClawHub npm Dependency Creates a Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 14–19
Vulnerability Type: Unpinned third-party npm dependency
Risk Level: MediumVulnerable Code
yaml install: - id: node kind: node package: clawhub bins: ["clawhub"] label: "Install ClawHub CLI (npm)"Technical Analysis
The installation configuration identifies the npm package
clawhubwithout specifying an exact version or integrity constraint. Consequently, installation may resolve to whichever package release is current at that time rather than the version reviewed alongside this skill.This creates a supply-chain exposure: if a future package version is compromised, maliciously maintained, or otherwise unsafe, installing the skill could introduce unreviewed code. npm packages may execute lifecycle scripts during installation, and the resulting
clawhubexecutable runs when the skill performs search, creation, login, or publishing operations.No evidence establishes that the current
clawhubpackage is malicious. The confirmed issue is the absence of dependency version and integrity controls.Attack Path
- An attacker compromises the npm package, its maintainer account, or a future release process.
- The attacker publishes a malicious version under the expected
clawhubpackage name. - The skill installation mechanism resolves the unpinned dependency to that malicious release.
- Malicious code executes through an npm installation lifecycle script or when the installed
clawhubbinary is invoked. - The code operates with the permissions and environmental access of the user or agent running the installation or command.
Impact Assessment
Successful exploitation could permit arbitrary code execution with the installing user's privileges. Depending on the execution environment, exposed resources could include project files, environment variables, authentication material accessible to th ...[truncated 365 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
clawhubto an exact, reviewed version rather than allowing resolution to an arbitrary current release. - Use lockfile or integrity metadata, where supported by the skill installation system, to verify the expected package artifact.
- Restrict installation to the official npm registry and verify the package publisher and provenance.
- Review package lifecycle scripts and release changes before upgrading the pinned version.
- Perform installation and CLI execution in a sandbox or least-privileged environment with access only to required files and credentials.
- Disable npm lifecycle scripts during installation when they are unnecessary and the surrounding framework supports doing so.
- Pin
