T08 · Insecure Dependencies
- Location
SKILL.md:8- Finding
Unpinned Package Execution and Remote Skill Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 8–9
Vulnerability Type: Unpinned third-party package execution and mutable remote Skill installation
Risk Level: MediumComplete Code Snippet:
markdown > **Consolidated (Δ9 v2):** New installs → `lygo-champion-council`. This slug is legacy retention only. > `npx clawhub@latest install deepseekoracle/lygo-champion-council`Technical Analysis
The documented command uses
npxto resolve and execute the latest published version of theclawhubnpm package. The package version is not pinned, and the remotely installeddeepseekoracle/lygo-champion-councilSkill is not constrained by an immutable version, cryptographic digest, or verified signature.Therefore, the effective code and Skill instructions executed by a user can change after this repository has been audited. Compromise of the npm package, its publisher account, the package registry, or the remote Skill publisher could turn the recommended command into a supply-chain delivery mechanism. The audited repository does not itself contain a malicious payload; the risk arises when a user follows this mutable installation instruction.
Attack Path
- An attacker compromises the
clawhubnpm package, its publisher account, or the remote successor Skill. - The attacker publishes a malicious release or replaces the remotely resolved Skill content.
- A user or agent follows the command in
SKILL.md. npxdownloads and executes the then-currentclawhub@latestpackage.- The package installs the remotely resolved
deepseekoracle/lygo-champion-councilSkill. - Attacker-controlled package code may execute locally, or attacker-controlled Skill instructions may be loaded in subsequent agent activity.
Impact Assessment
Package code launched through
npxruns with the privileges of the invoking user. Depending on the malicious upstream payload and loc ...[truncated 411 chars]- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
clawhub@latestwith an exact, reviewed package version. - Pin the successor Skill to an immutable version or content digest.
- Publish expected SHA-256 digests or signed provenance and verify them before installation.
- Use lockfiles and integrity metadata where supported.
- Prefer downloading the package and Skill into an isolated location for review before executing or activating them.
- Run installation with least privilege in a sandbox or disposable environment.
- Document the trusted publisher identity and a procedure for verifying signatures, hashes, and provenance.
- Periodically review pinned versions before intentionally upgrading them.
- Replace
