T08 · Insecure Dependencies
Error
- Location
SKILL.md:14- Finding
Unpinned and Unverifiable Financial Plugin Installation
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 14–20
Vulnerability Type: Unpinned third-party dependency with sensitive wallet and live-trading capabilities
Risk Level: HighVulnerable Code Snippet
markdown ## Setup Install the OpenClaw plugin: ```bash openclaw plugins install devbox-pocZero user interaction. Wallet auto-generated on first run.
text ### Technical Analysis The setup instructions install the registry-resolved `devbox-poc` plugin without specifying an immutable version, integrity digest, verified publisher, or trusted source repository. The plugin implementation is not included in the audited project, so its behavior cannot be inspected or compared against the documentation. The dependency is particularly sensitive because the document states that it automatically generates a wallet and supports deployment to live trading. The declared description of a “POC demo with mock data” also conflicts with the documented live-trading behavior, making the plugin's actual operational scope unclear. An attacker who compromises the package, publisher account, registry resolution process, or an unpinned future release could cause users to install modified code under the legitimate-looking plugin name. ### Attack Path 1. An attacker compromises the plugin publisher account or distribution registry, substitutes the package, or publishes a malicious future release under the resolved package name. 2. A user follows the documented setup command without receiving a version or integrity guarantee. 3. OpenClaw resolves, installs, and loads the attacker-controlled plugin. 4. The plugin executes with whatever wallet, filesystem, network, and trading permissions the OpenClaw environment grants it. 5. The malicious plugin can target generated wallet material, falsify strategy results, alter deployment parameters, or initiate unauthorized financial operations. ### Impact Assessment Successful exploitation may allow execution of ...[truncated 500 chars]- Remediation
View remediation
Remediation Suggestions
- Pin the plugin to a reviewed, immutable version rather than resolving the latest registry release.
- Verify the package with a cryptographic integrity digest and authenticated publisher signature.
- Document the canonical source repository, package registry, publisher identity, and verification procedure.
- Include or vendor the reviewable plugin implementation when practical so its wallet and trading behavior can be audited.
- Require explicit, informed user confirmation before generating a wallet or enabling live trading.
- Separate mock backtesting from live deployment and clearly identify which mode is active.
- Apply least-privilege controls so the plugin receives only the filesystem, network, wallet, and trading permissions required for the selected operation.
- Document how wallet keys are generated, encrypted, stored, accessed, backed up, and deleted.
- Require transaction previews, explicit deployment confirmation, configurable spending limits, and an emergency disable mechanism before any live financial action.
- Re-audit every plugin update before changing the pinned version.