T08 · Insecure Dependencies
- Location
SKILL.md:27- Finding
Unpinned Remote Package Execution Through npx
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:27-29
Vulnerability Type: Supply-chain exposure through mutable package resolution
Risk Level: Mediumbash npx clawhub@latest install openclaw-cn-installerTechnical Analysis
The documented installation command instructs users to download and execute the package currently associated with the mutable
latesttag. The effective code executed bynpxcan therefore change after this Skill has been reviewed.No malicious dependency is present in the audited project itself. However, the command creates a supply-chain execution boundary: compromise of the registry account, package publication process, registry resolution, or a future release could cause users to execute unaudited code. The package runs with the privileges of the user invoking
npx.Attack Path
- An attacker compromises the publisher account, release pipeline, or package associated with
clawhub. - The attacker publishes a malicious version and assigns it the
latestdistribution tag. - A user follows the installation command in
SKILL.md. npxretrieves and executes the attacker-controlled package.- The malicious package can access files, credentials, network resources, and processes available to the invoking user.
Impact Assessment
Successful exploitation permits arbitrary code execution under the invoking user's account. This could expose OpenClaw configuration, API keys, source code, SSH credentials, and other user-readable data. It could also modify user-owned files or establish user-level persistence. The command does not inherently grant administrator or root privileges, so the immediate scope is limited to the invoking user's permissions.
- An attacker compromises the publisher account, release pipeline, or package associated with
- Remediation
View remediation
Remediation Suggestions
- Replace the mutable
latesttag with an exact, reviewed package version. - Publish and document a cryptographic checksum or other verifiable provenance information for the expected installer.
- Use a lockfile or similarly reproducible installation mechanism where supported.
- Restrict installation to the expected registry and verify the package publisher and repository before execution.
- Recommend running the installer as an unprivileged user and reviewing downloaded code before execution in sensitive environments.
- Replace the mutable
