T08 · Insecure Dependencies
- Location
SKILL.md:39- Finding
Unpinned Third-Party Skill Installation Creates a Supply-Chain Risk
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 39-46
Vulnerability Type: Unpinned third-party dependencies
Risk Level: Mediummarkdown **Dependencies**: `leegitw/constraint-engine` (for enforcement integration) ```bash # Install with dependencies openclaw install leegitw/context-verifier openclaw install leegitw/failure-memory openclaw install leegitw/constraint-engine openclaw install leegitw/safety-checkstext ### Technical Analysis The documented installation workflow instructs users to install four registry-resolved Skills without specifying immutable versions, commit identifiers, or integrity hashes. Consequently, the installed content is determined by the state of the package registry at installation time rather than by the content reviewed during this audit. The workflow also installs `context-verifier` and `failure-memory`, although the dependency declaration identifies only `constraint-engine` as an integration dependency. Their implementations are not included in this project and could not be audited. This unnecessarily expands the trusted dependency set and supply-chain attack surface. The issue does not establish that any currently published dependency is malicious. The vulnerability is that mutable, unaudited upstream content is trusted by default and may change after this Skill has been reviewed. ### Attack Path 1. An attacker compromises one of the referenced publisher accounts, package repositories, release processes, or registry entries. 2. The attacker publishes a modified Skill under one of the documented package names. 3. A user follows the installation commands in `SKILL.md`. 4. OpenClaw resolves the package name to the attacker-modified, mutable release because no reviewed version or integrity digest is specified. 5. The malicious dependency receives whatever execution, tool, file, or Agent capabilities the OpenClaw environment grants to installed Skills. 6 ...[truncated 953 chars]- Remediation
View remediation
Remediation Suggestions
- Pin every dependency to an exact, reviewed version rather than resolving the latest registry release.
- Where supported, pin an immutable source commit and verify a cryptographic checksum or signed provenance record before installation.
- Document the purpose and security rationale for each dependency.
- Remove
context-verifierandfailure-memoryfrom the default installation sequence unless they are required for the advertised functionality. - Separate optional integrations from the minimum installation path so users do not implicitly grant trust to unnecessary packages.
- Maintain a reviewed dependency lock file or manifest recording package names, exact versions, hashes, source repositories, and signer identities.
- Re-audit dependencies before updating pinned versions and configure the runtime to grant each installed Skill only the minimum required permissions.
