T08 · Insecure Dependencies
- Location
SKILL.md:58- Finding
Unpinned npm Dependency Installed Directly into the OpenClaw Application Directory
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:58-60,SKILL.md:133-135,references/windows-setup.md:44-46
Vulnerability Type: Unpinned third-party dependency installation
Risk Level: MediumVulnerable Code
powershell cd "D:\Program Files\OpenClaw\resources\openclaw" npm install node-llama-cppThe same installation procedure appears in both the primary Skill instructions and the Windows setup reference.
Technical Analysis
The command installs
node-llama-cppwithout specifying an exact version, lockfile, package integrity value, or approved release digest. npm therefore resolves the package version from the registry at installation time, meaning the installed code can differ from the version assessed when this Skill was published.npm dependencies can execute lifecycle scripts during installation. This package can also involve native components or downloaded precompiled binaries. Installing it directly into the deployed OpenClaw application directory expands the effect of a compromised or unexpectedly changed dependency beyond an isolated development environment.
This is a supply-chain weakness rather than evidence that
node-llama-cppis malicious.Attack Path
- An attacker compromises the package registry account, an upstream release, a transitive dependency, or a binary distribution endpoint.
- A malicious or vulnerable package version becomes the version selected by the unpinned installation command.
- A user follows the Skill and runs
npm install node-llama-cpp. - npm downloads the mutable package and dependency graph.
- Package lifecycle logic or native-component installation runs with the privileges of the invoking user.
- The altered dependency is placed in OpenClaw’s application tree and can subsequently execute when local embedding functionality is loaded.
Impact Assessment
Successful exploitation could execute code with the privileges of the acco ...[truncated 437 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
node-llama-cppto an exact version that has been tested and approved by OpenClaw. - Supply a reviewed lockfile and use
npm cirather than an unconstrainednpm install. - Document expected package and binary integrity hashes and verify them before use.
- Prefer an official OpenClaw release that bundles or explicitly declares a compatible dependency version.
- Review package lifecycle scripts and the provenance of native binaries before installation.
- Perform installation with the least-privileged account capable of updating the intended application directory.
- Consider installing and validating the dependency in an isolated staging copy before modifying the deployed application.
- Pin
