T08 · Insecure Dependencies
- Location
SKILL.md:18- Finding
Unpinned and Unverifiable Third-Party Plugin Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 18–20
Vulnerability Type: Unpinned third-party dependency installation
Risk Level: MediumVulnerable Code Snippet:
bash openclaw plugins install clawreachTechnical Analysis
The installation command resolves the
clawreachplugin by name without specifying an immutable version, package digest, trusted registry, publisher identity, checksum, or cryptographic signature. The project contains onlySKILL.md; therefore, the executable plugin code installed by this command was not available for inspection and cannot be verified against the documented functionality.Name-only resolution means the code ultimately installed can change independently of the reviewed skill document. A compromised registry account, package-name takeover, dependency-confusion condition, or malicious future release could cause the command to retrieve and activate code that differs from the version originally intended. The documentation also states that the gateway restarts automatically after installation, potentially causing the newly installed component to load immediately.
Attack Path
- An attacker compromises the publisher account or plugin registry, takes control of the resolved package name, or publishes a malicious release through an unsafe source.
- The attacker distributes a modified
clawreachpackage containing unauthorized behavior. - A user follows the documented command, which resolves the plugin by its mutable name rather than an audited immutable version or digest.
- The plugin manager downloads and installs the attacker-controlled release.
- The gateway restarts and loads the installed plugin.
- The malicious plugin executes with whatever filesystem, network, tool, credential, and gateway privileges are granted to the plugin runtime.
This path is conditional on compromise or unsafe resolution of the external package. The reviewed file do ...[truncated 718 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the plugin to an audited, immutable version rather than resolving the latest release by name.
- Prefer a content-addressed digest and require the installer to verify it before execution.
- Explicitly identify the trusted registry, verified publisher, and canonical source repository.
- Require cryptographic package signatures and fail installation if signature validation is unavailable or unsuccessful.
- Include the plugin source code or a reproducible-build reference in the audit scope so its behavior can be independently verified.
- Disable automatic activation or gateway restart until package integrity and requested permissions have been reviewed.
- Run the plugin with least privilege, restricting filesystem access, credentials, tools, and outbound network destinations to those strictly required.
- Maintain a reviewed allowlist of acceptable versions and monitor the publisher and registry for ownership or integrity changes.
