T08 · Insecure Dependencies
- Location
SKILL.md:21- Finding
Unpinned Remote Package Download and Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 21
Vulnerability Type: Unverified execution of a mutable third-party package
Risk Level: HighVulnerable Code:
bash npx -y openclaw uninstall --all --yes --non-interactiveTechnical Analysis
The documented command instructs
npxto resolve, download, and execute the current registry version of theopenclawpackage. No exact version or package integrity value is specified, so the code executed by users can change after this Skill has been audited.The
-yoption automatically accepts installation prompts, while--yes --non-interactivesuppresses application-level confirmation. These options reduce the user's opportunity to inspect the resolved package and operation before execution. A compromised package publisher, registry account, package release, or dependency could therefore turn this uninstall command into arbitrary code execution.This behavior is not strictly necessary for the declared uninstall functionality. The already-installed
openclawexecutable shown elsewhere in the document is a safer option because it does not require downloading mutable code during uninstallation.Attack Path
- An attacker compromises the
openclawpackage, a package maintainer account, or a dependency incorporated into a new release. - The attacker publishes a malicious version under the package name resolved by
npx. - A user follows the documented uninstallation instructions.
npx -ydownloads and executes the malicious package without version pinning or interactive package approval.- Malicious package lifecycle scripts or runtime code execute with the privileges of the invoking user.
Impact Assessment
Successful exploitation permits arbitrary code execution under the invoking user's account. This can expose files, environment variables, API credentials, OpenClaw state, and any other resources accessible to that account ...[truncated 203 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
-
Prefer the locally installed and previously verified CLI:
bash openclaw uninstall --all --yes --non-interactive -
If remote package execution must remain available, pin an explicitly reviewed version rather than resolving the latest release:
bash npx --yes openclaw@<reviewed-version> uninstall --all --yes --non-interactive -
Verify the package publisher, registry, exact version, and published integrity metadata before execution.
-
Avoid recommending elevated execution and document that the command should run with ordinary user privileges.
-
Remove automatic confirmation where practical so users can inspect the package and operation before execution.
-
Prefer an authenticated, integrity-locked installation process over ad hoc execution from a mutable registry.
-
