T08 · Insecure Dependencies
- Location
SKILL.md:40- Finding
Unpinned Global Installation of a Third-Party npm Package
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:40
Vulnerability Type: Unpinned and globally installed third-party dependency
Risk Level: Mediumbash npm install -g openclawTechnical Analysis
The skill directs the user or agent to install the latest available version of the
openclawnpm package globally. The command does not specify an exact reviewed version, enforce an integrity value, use a lockfile, or require package provenance verification.npm packages can execute lifecycle scripts during installation. Consequently, a compromised package release, maintainer account, transitive dependency, or package distribution channel could cause arbitrary code to run with the permissions of the account executing the command. Global installation also exposes package-provided executables broadly within that account's environment.
The package name is consistent with the skill's stated purpose, and the reviewed file does not prove that the current package is malicious. The vulnerability is the unsafe and mutable supply-chain installation practice.
Attack Path
- An attacker compromises the
openclawnpm package, its publisher account, or one of its transitive dependencies. - The attacker publishes a malicious release or introduces a malicious installation lifecycle script.
- A user or agent follows the instruction at
SKILL.md:40. - npm resolves the unpinned dependency to the attacker-controlled release.
- npm executes applicable lifecycle scripts with the invoking user's permissions.
- The malicious package can access data available to that user and may subsequently intercept workspace information or Channel credentials entered during OpenClaw configuration.
Impact Assessment
Successful exploitation could provide arbitrary code execution under the invoking user's account. The accessible scope may include:
- Files and environment variables readable or writable by the user.
- OpenClaw workspace configuration and operat ...[truncated 438 chars]
- An attacker compromises the
- Remediation
View remediation
Remediation Suggestions
- Pin the dependency to an exact version that has undergone security review, for example:
bash npm install -g openclaw@<reviewed-exact-version> - Verify that the package publisher and registry match the project's official distribution information.
- Document and validate package provenance, signatures, or published integrity hashes before installation.
- Review package lifecycle scripts and transitive dependencies before recommending execution.
- Prefer a project-local dependency governed by a committed lockfile over a global installation where operationally possible.
- Consider using a verified standalone release or isolated execution environment with minimal filesystem and credential access.
- Test upgrades separately and update the pinned version only after reviewing the new release and dependency changes.
- Pin the dependency to an exact version that has undergone security review, for example:
