T08 · Insecure Dependencies
- Location
SKILL.md:42- Finding
Unpinned Privileged Third-Party Plugin Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 42-47
Vulnerability Type: Unpinned third-party dependency with privileged tool access
Risk Level: Mediumbash ## Install Install the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat. openclaw plugins install clawhub:clawlink-plugin openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json openclaw gateway restartTechnical Analysis
The installation command references
clawhub:clawlink-pluginwithout an immutable version, cryptographic digest, or other integrity constraint. The subsequent command explicitly adds the plugin to the permitted tool list, and the gateway restart activates it.Because the installed artifact is mutable from the perspective of this reviewed skill, its effective behavior can change independently of
SKILL.md. The skill does not provide a mechanism to verify that the downloaded package is the same package that was previously audited. This creates a supply-chain exposure if the registry, publisher account, package namespace, or plugin release process is compromised.The reviewed file does not establish that the plugin is malicious. The issue is that a privileged external component is installed and trusted without reproducible version or integrity verification.
Attack Path
- An attacker compromises the plugin publisher account, package registry, release pipeline, or an otherwise mutable unpinned release.
- The attacker publishes a modified artifact under the existing
clawlink-pluginidentifier. - A user follows the skill instructions and runs
openclaw plugins install clawhub:clawlink-plugin. - OpenClaw resolves and installs the attacker-controlled package because no trusted version or digest is specified.
- The configuration command allowlists the installed plugin.
- Restarting the gateway ...[truncated 999 chars]
- Remediation
View remediation
Remediation Suggestions
- Pin the plugin to a specifically reviewed version rather than resolving the package by an unversioned name.
- Where supported, pin and verify an immutable cryptographic digest or signed package identity.
- Verify the publisher signature, registry provenance, and package checksum before installation and activation.
- Document the exact plugin permissions, OAuth scopes, network destinations, and data categories available to the plugin.
- Apply least privilege by allowing only the specific Tally operations required for the user's request instead of granting broader plugin access.
- Require separate, explicit user confirmation before installing the plugin, changing the tool allowlist, and restarting the gateway.
- Review the resolved plugin artifact and its transitive dependencies before deployment.
- Establish a trusted update process that re-audits new versions and rejects unexpected package or digest changes.
