T08 · Insecure Dependencies
- Location
SKILL.md:14- Finding
Unpinned Third-Party Dependencies Allow Supply-Chain Code Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:14,SKILL.md:54, andreferences/generated-files.md:46
Vulnerability Type: Unpinned and insufficiently verified npm dependencies
Risk Level: MediumVulnerable Code Snippets
SKILL.md:14:markdown 3. For the current tested OpenClaw build, install `memory-lancedb-pro` together with a matching local `openclaw` package inside the generated state directory. This keeps `openclaw/plugin-sdk` resolvable for the memory plugin on newer releases.SKILL.md:54:markdown - The current tested memory install path is state-local npm dependencies, not `openclaw plugins install memory-lancedb-pro`, because the plugin still expects local `openclaw/plugin-sdk` resolution.references/generated-files.md:46:markdown - `package.json` and `package-lock.json` Written when core memory dependencies are installed. The kit uses state-local `openclaw` plus `memory-lancedb-pro` packages so the memory plugin can resolve `openclaw/plugin-sdk` on the current tested OpenClaw release.Technical Analysis
The workflow directs the Agent to install
openclawandmemory-lancedb-prowithout specifying exact, reviewed versions, integrity hashes, or a pre-generated trusted lockfile. The phrase “matching localopenclawpackage” does not impose a deterministic or verifiable version constraint.Although the generated workspace is expected to contain
package-lock.json, the documentation states that this file is written when dependencies are installed. Therefore, the initial resolution and installation occur before the resulting lockfile can provide reproducibility. npm lifecycle scripts may also run during this initial installation.A mutable package release, compromised maintainer account, malicious transitive dependency, or altered dependency resolution could consequently introduce attacker-controlled code. The referenced bootstrap script is absent ...[truncated 1631 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin
openclaw,memory-lancedb-pro, and all optional plugins to exact reviewed versions rather than ranges or implicit latest releases. - Include a reviewed
package-lock.jsonin the Skill package and usenpm ciso installation fails if dependency resolution differs from the lockfile. - Verify registry provenance and package integrity before installation, including expected package owners and integrity hashes.
- Use
npm ci --ignore-scriptswhere compatible. If lifecycle scripts are required, document and explicitly approve each required script before allowing it to execute. - Perform dependency installation under a dedicated, least-privileged account without access to unrelated credentials or sensitive directories.
- Add automated dependency auditing and provenance checks to the release process.
- Include the referenced bootstrap script in the package so reviewers can verify installation commands, registry selection, version constraints, error handling, and lifecycle-script behavior.
- Document a controlled upgrade procedure requiring review and lockfile regeneration before dependency versions change.
- Pin
