T08 · Insecure Dependencies
- Location
SKILL.md:19- Finding
Unpinned Global Installation of Third-Party CLI and Skill
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 19-24
Vulnerability Type: Unverified and mutable third-party dependency installation
Risk Level: MediumVulnerable Code:
bash # Install the ClawHub CLI npm install -g clawhub # Install this skill clawhub install claw-clawbridgeTechnical Analysis
The installation instructions retrieve and install the current registry versions of both the
clawhubnpm package and theclaw-clawbridgeSkill without version pins, integrity hashes, lockfiles, signature verification, or other provenance controls.Installing the npm package globally expands its potential effect to the user's environment. npm packages can define installation lifecycle scripts, so a compromised or malicious package release could execute code during installation with the privileges of the user running the command. The subsequent Skill installation is also mutable because no reviewed version or artifact digest is specified.
This is a supply-chain risk rather than evidence that the currently documented packages are malicious. Exploitation depends on compromise, substitution, or publication of an unsafe release and on a user executing the documented commands.
Attack Path
- An attacker compromises the package publisher, registry account, distribution channel, or a future release of
clawhuborclaw-clawbridge. - The attacker publishes a malicious release under the expected package or Skill name.
- A user follows the documentation and executes
npm install -g clawhub. - npm retrieves the mutable latest release; malicious package content or applicable lifecycle scripts execute under the invoking user's account.
- The compromised CLI may then alter the workspace or install attacker-controlled Skill content when
clawhub install claw-clawbridgeis executed.
Impact Assessment
Successful exploitation could allow arbitrary code execution with the privileges o ...[truncated 541 chars]
- An attacker compromises the package publisher, registry account, distribution channel, or a future release of
- Remediation
View remediation
Remediation Suggestions
- Pin the CLI and Skill to explicitly reviewed versions rather than installing mutable latest releases.
- Publish and verify cryptographic integrity hashes or signed release artifacts through a documented trusted channel.
- Provide the canonical package registry, publisher identity, and source repository so users can validate provenance.
- Use a lockfile or a verified archive where supported.
- Avoid global installation where possible; install the CLI in an isolated project or disposable environment with minimal privileges.
- Disable npm lifecycle scripts during installation when they are not required, and document any scripts that are necessary.
- Never instruct users to run installation commands as root or through
sudo. - Re-audit each pinned release before updating the documented version and integrity value.
