T08 · Insecure Dependencies
- Location
SKILL.md:14- Finding
Unpinned Package Execution in Installation Command
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:14
Vulnerability Type:T08: Insecure Dependencies
Risk Level: HighVulnerable Code
yaml installCommand: npx clawhub install gougoubi-pump-lifecycleTechnical Analysis
The installation command invokes
clawhubthroughnpxwithout specifying an exact package version or verifying package integrity. If an approved local version is unavailable,npxmay retrieve and execute the package currently published under that name in the configured npm registry.Consequently, the code executed during installation is mutable and is not necessarily the same code that existed when this Skill was audited. Compromise of the package, its publisher account, the registry, or the dependency chain could therefore introduce arbitrary installation-time behavior.
The issue concerns the
clawhubinstaller invoked by the command. The reviewedSKILL.mddoes not itself contain an embedded malicious payload, and the audit found no evidence that the current package is malicious. The vulnerability is the absence of version and integrity controls at an executable supply-chain boundary.Attack Path
- An attacker compromises the
clawhubpublishing account, package, registry delivery path, or one of its install-time dependencies. - The attacker publishes a malicious release under the expected package name or alters a dependency resolved by that release.
- A user follows the documented command while no trusted local executable overrides package retrieval.
npxresolves the mutable package release and executes its command.- The malicious package runs with the operating-system permissions and environment available to the installing user.
Impact Assessment
Successful exploitation can provide arbitrary code execution under the installing user's account. Depending on that account's privileges and environment, an attacker could access project files, wallet ...[truncated 853 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
-
Pin the installer to an explicitly reviewed version instead of resolving the latest release:
yaml installCommand: npx --yes clawhub@<reviewed-version> install gougoubi-pump-lifecycle -
Prefer a package manager workflow backed by a committed lockfile so the complete transitive dependency graph is reproducible.
-
Verify package provenance and integrity using registry integrity metadata, trusted signatures, or an approved internal artifact repository.
-
Disable lifecycle scripts where operationally possible, or review all install-time scripts before execution.
-
Execute installation from a minimally privileged, isolated environment without wallet secrets, production credentials, or unnecessary filesystem access.
-
Establish a controlled update process in which new installer versions and dependency changes are reviewed and tested before the pinned version is changed.
-
