T08 · Insecure Dependencies
- Location
SKILL.md:47- Finding
Unpinned Third-Party Plugin Installation and Allowlisting
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 47–49
Vulnerability Type: Unpinned executable dependency from an external package registry
Risk Level: MediumVulnerable Code
bash openclaw plugins install clawhub:clawlink-plugin openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json openclaw gateway restartThe allowlisting and restart commands are also repeated in the troubleshooting instructions at
SKILL.md:268-269.Technical Analysis
The installation command identifies
clawlink-pluginonly by its mutable package name. It does not specify an audited version, immutable digest, signature, checksum, or other integrity constraint. The subsequent commands add the installed plugin to OpenClaw's allowed tools and restart the gateway so that it becomes active.Because the reviewed project contains only
SKILL.mdand does not include the plugin's implementation, the plugin's effective behavior cannot be verified from this artifact. A future package update, compromised publisher account, or compromised distribution channel could therefore cause users following these instructions to load code that differs from the code originally reviewed.This is a supply-chain risk rather than evidence that the current external package is malicious.
Attack Path
- An attacker compromises the plugin publisher account, package registry, release process, or another relevant distribution component.
- The attacker publishes a modified package under the mutable
clawlink-pluginidentifier. - A user or agent follows the documented installation command without an immutable version or digest.
- OpenClaw retrieves and installs the attacker-controlled package.
- The configuration command allowlists the plugin.
- The gateway restart activates the installed plugin.
- The plugin executes within its granted OpenClaw environment and may misuse exposed integration capabilities or ac ...[truncated 728 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the plugin to a specific, audited release rather than installing a mutable package name.
- Prefer an immutable artifact digest and verify it before installation.
- Require cryptographic package signatures and validate the publisher identity and signature chain.
- Record the expected version, digest, provenance, and review date in the Skill documentation.
- Review the plugin implementation and its transitive dependencies before allowlisting it.
- Restrict the plugin to the minimum Google Chat tools and permissions required; avoid broad or unrelated tool access.
- Run the plugin in a sandbox with limited filesystem, network, process, and credential access.
- Apply the same pinned and verified installation procedure to the troubleshooting path at
SKILL.md:268-269. - Monitor installed plugin versions and alert on unauthorized package or integrity changes.
