T08 · Insecure Dependencies
- Location
SKILL.md:31- Finding
Unpinned Third-Party Plugin Installation and Activation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 31–33
Vulnerability Type: Unpinned and unauditable third-party dependency
Risk Level: MediumVulnerable Code
bash openclaw plugins install clawhub:clawlink-plugin openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json openclaw gateway restartTechnical Analysis
The skill instructs users to install a remotely sourced plugin without specifying an immutable version, checksum, signature, or source commit. It then explicitly adds that plugin to the allowed tool configuration and restarts the OpenClaw gateway to activate it.
Because this project contains only
SKILL.mdand does not include the plugin implementation, the installed behavior, requested permissions, OAuth handling, and data-processing logic cannot be verified by auditing this package. The effective implementation may also change after review if the mutable package reference resolves to a later release.This creates a supply-chain trust boundary: the safety of the skill depends on the integrity of the package registry, publisher account, distribution process, and all transitive components of
clawlink-plugin.Attack Path
- An attacker compromises the plugin publisher account, package registry entry, release pipeline, or an upstream dependency.
- The attacker publishes a malicious release under the existing mutable
clawlink-pluginpackage identifier. - A user follows line 31 and installs the compromised release because no version or integrity value is pinned.
- Line 32 adds the plugin to the allowed tool set.
- Line 33 restarts the gateway, activating the compromised implementation.
- Subsequent legitimate-looking ClawLink operations execute attacker-controlled plugin logic.
Impact Assessment
A compromised plugin could execute with the permissions granted to the OpenClaw plugin context. Depending on runtime isolation and available interfaces, it could manipulate tool behavior or ...[truncated 425 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the plugin to an immutable, independently audited version rather than using a mutable package identifier.
- Verify a publisher signature and cryptographic package checksum before installation.
- Publish the plugin source and tie each distributed package to a verifiable source commit and reproducible build.
- Document the plugin's exact runtime permissions, network destinations, credential access, and data-retention behavior.
- Apply least privilege so the plugin can access only the LinkHut operations and data required for its stated functionality.
- Require explicit user approval before installation, allow-list modification, and gateway activation.
- Audit and pin transitive dependencies, and use automated dependency integrity and provenance checks.
- Provide a rollback procedure and revoke affected OAuth sessions if package integrity is later questioned.
