T08 · Insecure Dependencies
- Location
SKILL.md:31- Finding
Unpinned npm Installer Is Downloaded and Executed via npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 31–34
Vulnerability Type: Unpinned third-party executable dependency
Risk Level: Mediumbash npx clawhub@latest install deepseekoracle/lygo-open-claw # or canonical: npx clawhub@latest install deepseekoracle/lygo-sovereign-clawTechnical Analysis
The documented installation procedure invokes
npxwith the mutableclawhub@latestversion specifier. If the package is not already available locally,npxcan retrieve the currently published package from the npm registry and execute its command-line entry point.The
latesttag is mutable and provides no guarantee that operators will execute the same code that was available when this Skill was audited. The command also does not specify an integrity hash or another mechanism for verifying that the downloaded installer matches a reviewed artifact. Consequently, compromise of the npm package, its publisher account, the distribution channel, or a future release could introduce arbitrary installer behavior.This finding does not establish that the current
clawhubpackage is malicious. It identifies a supply-chain trust boundary created by downloading and executing an unpinned dependency.Attack Path
- An attacker compromises the npm publisher account, package, release process, or another component capable of changing the release referenced by the
latesttag. - The attacker publishes a modified release and assigns it to
clawhub@latest. - An operator follows the installation command documented in
SKILL.md. npxretrieves and executes the attacker-controlled package entry point.- The malicious installer performs actions with the operating-system permissions and environmental access of the invoking user.
Impact Assessment
Successful exploitation could permit arbitrary code execution under the privileges of the user running the installation command. Depending on that use ...[truncated 454 chars]
- An attacker compromises the npm publisher account, package, release process, or another component capable of changing the release referenced by the
- Remediation
View remediation
Remediation Suggestions
- Replace
clawhub@latestwith an exact, reviewed package version, for exampleclawhub@X.Y.Z. - Verify the package against a trusted integrity digest or signed provenance record before execution.
- Document the expected publisher, registry, package version, and checksum so operators can independently validate the artifact.
- Run the installer with least privilege in an isolated environment without unnecessary credentials or sensitive environment variables.
- Avoid elevated or administrative execution unless it is strictly required and separately justified.
- Establish a controlled update process in which new installer versions are reviewed before the documented version is changed.
- Replace
