T08 · Insecure Dependencies
- Location
SKILL.md:10- Finding
Automatically Installed Dependency Is Not Version-Pinned
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:10-15andSKILL.md:99-103
Vulnerability Type: Unpinned third-party dependency installation
Risk Level: MediumVulnerable Code
yaml metadata: openclaw: requires: anyBins: - node install: - node: playwrightThe dependency behavior is also documented as follows:
markdown ## Dependency Notes When installing the Skill, OpenClaw automatically runs `npm install playwright` (including the Chromium browser). Image generation invokes `node render.js` to render HTML as PNG. No manual intervention, API key, or Python is required.Technical Analysis
The Skill instructs OpenClaw to install
playwrightwithout specifying an exact reviewed version. No dependency lockfile or integrity hash is present in the audited project. Consequently, the code installed during a future deployment is not necessarily the same code that was implicitly trusted when this Skill was reviewed.Package installation can execute third-party installation and lifecycle logic with the permissions of the OpenClaw process. Playwright also downloads or provisions substantial browser components. Although the audit found no evidence that the current package name is a typosquat or that Playwright itself is malicious, unconstrained dependency resolution creates a supply-chain exposure: a compromised registry account, malicious future release, registry substitution, or unexpected dependency-tree change could introduce executable code after review.
Attack Path
- An attacker compromises the package publication process, registry account, configured package registry, or a transitive dependency used by a future
playwrightrelease. - The attacker publishes or serves a malicious package version under the dependency resolution accepted by
npm install playwright. - A user installs or reinstalls the Skill.
- OpenClaw automatica ...[truncated 873 chars]
- An attacker compromises the package publication process, registry account, configured package registry, or a transitive dependency used by a future
- Remediation
View remediation
Remediation Suggestions
- Replace the floating dependency with an exact, reviewed Playwright version rather than a package name that resolves to the latest release.
- Add and enforce a lockfile containing resolved versions and integrity hashes.
- Configure installation to use a trusted registry over authenticated TLS, and reject unexpected registry overrides.
- Use reproducible installation such as
npm ciinstead of unconstrainednpm install. - Disable dependency lifecycle scripts where operationally possible, or explicitly review every required lifecycle script before permitting it.
- Pin and verify downloaded browser binaries or use a pre-reviewed browser image with integrity validation.
- Run installation and rendering in a sandboxed, non-privileged account with restricted filesystem and network access.
- Add automated dependency scanning and require review before updating the pinned dependency or lockfile.
