T08 · Insecure Dependencies
- Location
SKILL.md:14- Finding
Unpinned npm Package Execution Through npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 14
Vulnerability Type: Supply-chain risk from a mutable third-party dependency
Risk Level: MediumVulnerable Code Snippet:
bash npx clawhub@latest install deepseekoracle/lygo-champion-councilTechnical Analysis
The documented installation command instructs users to execute the mutable
latestrelease of the third-partyclawhubnpm package. Because neither an exact package version nor an integrity digest is specified, the code executed by this command may differ from the version that was available when the Skill was audited.npxmay download the selected package and execute its CLI code locally. Consequently, compromise of the npm package, its publisher account, a future release, or a transitive dependency could introduce arbitrary executable behavior without requiring any change to this repository. The local project scripts themselves do not retrieve or execute remote code; the risk arises when a user follows the documented installation command.Attack Path
- An attacker compromises the
clawhubnpm publisher account, release process, package, or relevant dependency. - The attacker publishes a malicious version and causes it to resolve under the
latestdistribution tag. - A user follows the installation instructions and runs
npx clawhub@latest install deepseekoracle/lygo-champion-council. npxdownloads and executes the attacker-controlled package version.- The malicious package runs with the permissions and environmental access of the invoking user.
Impact Assessment
Successful exploitation could permit arbitrary code execution under the installing user's account. Depending on that user's privileges and execution environment, an attacker could read or modify accessible files, obtain environment variables or credentials available to the process, alter installed content, initiate network connections, or establi ...[truncated 350 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Replace
@latestwith an exact, reviewed package version, for exampleclawhub@X.Y.Z. - Where the package manager and deployment process support it, verify the package with a trusted integrity digest or registry signature before execution.
- Record the approved package version and checksum in the installation documentation.
- Review and pin transitive dependencies through an appropriate lockfile when maintaining a local installation wrapper.
- Avoid running the installer with administrative privileges.
- Execute installation in a restricted environment with minimal filesystem, credential, and network access where practical.
- Establish a controlled update process in which newer versions are reviewed before the documented pin is changed.
- Replace
