T08 · Insecure Dependencies
- Location
SKILL.md:16- Finding
Unpinned Package Execution During Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 16–22
Vulnerability Type:T08: Insecure Dependencies
Risk Level: HighVulnerable Code
yaml install: "npx clawhub install deliberate-cold-exposure"shell npx clawhub install deliberate-cold-exposureTechnical Analysis
The documented installation process invokes
clawhubthroughnpxwithout specifying an exact package version or verifying a package integrity digest. Depending on the local environment and package-manager configuration,npxcan retrieve and immediately execute the currently resolved package from an external registry.The repository contains no lockfile, vendored installer, checksum, signature-verification procedure, or publisher-validation mechanism that would bind installation to the version reviewed during this audit. Consequently, the code executed during installation may differ from the content originally audited.
This creates a supply-chain execution boundary: compromise of the package publisher, registry account, package-resolution process, or a future release could result in arbitrary installer code running on a user's system.
Attack Path
- An attacker compromises the package publisher, registry account, or another component of the package distribution path.
- The attacker publishes a malicious version that resolves under the unversioned
clawhubpackage name. - A user follows the installation command from
SKILL.md. npxdownloads and executes the attacker-controlled package.- Malicious package lifecycle or installer code runs with the privileges of the invoking user.
Impact Assessment
Successful exploitation could provide arbitrary code execution with the current user's privileges. Depending on those privileges and the host configuration, the malicious package could access user-readable files, steal credentials available to the process, alter project files, make network ...[truncated 336 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
clawhubto a specific, reviewed version rather than allowing an unspecified current release to execute. - Commit an appropriate lockfile containing package integrity metadata.
- Verify registry provenance, publisher identity, signatures, and cryptographic integrity before execution.
- Document the authoritative package registry and expected package digest.
- Prefer an installation process that downloads and verifies the artifact before executing it.
- Review package lifecycle scripts and transitive dependencies for the pinned release.
- Run installation with the minimum necessary privileges and avoid elevated shells.
- Use automated dependency monitoring while requiring explicit review before changing the pinned version.
- Pin
