T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:19
- Finding
- Unpinned Third-Party Plugin Installation Creates a Supply-Chain Risk## Vulnerability Details **File Location**: `SKILL.md`, lines 19-23 **Vulnerability Type**: Unpinned third-party dependency installation **Risk Level**: Medium ### Vulnerable Code ```bash ## Installation (Do This First) When the human asks to install MoltGuard, or when you want to protect yourself: # Install the plugin openclaw plugins install @openguardrails/moltguard ``` ### Technical Analysis The installation command resolves `@openguardrails/moltguard` without specifying an exact version, integrity hash, signature, or immutable source reference. Consequently, the code installed at execution time can differ from the version represented by this reviewed skill document. This plugin occupies a security-sensitive position: the documentation states that it processes security detections, obtains and stores an API key, modifies OpenClaw configuration, and can interact with an external Core service. Installing a mutable package into that position means compromise of the package registry, publisher account, release process, or package namespace could introduce arbitrary plugin behavior. The GitHub URL in the metadata identifies an intended source but does not establish that the registry artifact downloaded by the command was built from the reviewed source. ### Attack Path 1. An attacker compromises the package publisher, package registry, release pipeline, or another component of the dependency supply chain. 2. The attacker publishes a malicious version under the expected package name. 3. A user or Agent follows the documented installation command without an explicit version constraint. 4. The package manager resolves and installs the attacker-controlled release. 5. The malicious plugin executes with the permissions granted to OpenClaw and may access data, configuration, or credentials available within that execution context. This path is conditional on a supply-chain compromise; the reviewed document does not itsel ...[truncated 521 chars]
- Remediation
- ## Remediation Suggestions - Pin the plugin to an exact, audited version rather than resolving the latest available release. - Verify the package with a cryptographic integrity hash and trusted publisher signature. - Document the authoritative registry and verify that the published artifact corresponds to the referenced source repository. - Use reproducible builds and publish verifiable provenance attestations for each release. - Require explicit user approval before installing or updating executable third-party components. - Review updates before deployment and avoid automatic transitions to unreviewed versions. - Run the plugin in a restricted environment with only the filesystem and network permissions required for its security-detection function.