T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:270
- Finding
- Unpinned ClawHub Skill Dependency Installation## Vulnerability Details **File Location**: `SKILL.md`, line 270 **Vulnerability Type**: `T08: Insecure Dependencies` **Risk Level**: Medium ### Vulnerable Code ```bash clawhub install clawdmint ``` ### Technical Analysis The documented installation command identifies the ClawHub package only by its mutable package name. It does not specify an immutable version, content digest, source commit, or cryptographic signature. Consequently, the content installed when a user executes this command may differ from the artifact reviewed during this audit. Compromise of the publisher account, package registry, or package release process could cause an altered Skill to be installed under the legitimate package name. The project also demonstrates use of the `@x402/fetch` payment dependency without a pinned version at line 370. Because this component is expected to interact with a wallet and automate USDC payments, users must ensure that the version installed by their surrounding application is explicitly pinned and independently reviewed. ### Attack Path 1. An attacker compromises the ClawHub publisher account, registry entry, or release process associated with `clawdmint`. 2. The attacker publishes a modified Skill under the same trusted package name. 3. A user executes `clawhub install clawdmint` as instructed. 4. ClawHub resolves the mutable name to the attacker-controlled release. 5. OpenClaw loads the modified Skill, which may introduce malicious instructions, request credentials, redirect transactions, or initiate additional downloads. ### Impact Assessment Successful exploitation could affect the privileges available to the OpenClaw process and any credentials or tools exposed to the installed Skill. Depending on the malicious replacement's content, the impact could include disclosure of the Clawdmint API key, manipulation of NFT deployment parameters, unauthorized network requests, or abuse of wallet-integrated payment f ...[truncated 184 chars]
- Remediation
- ## Remediation Suggestions - Pin the ClawHub Skill to a reviewed, immutable version rather than installing by package name alone. - Publish a SHA-256 digest or signed manifest for every supported release and require verification during installation. - Document the authoritative source repository, release commit, publisher identity, and signature-verification procedure. - Use dependency lockfiles and integrity metadata for applications that install `@x402/fetch`. - Review wallet-capable dependencies before use and restrict them to the required chain, payment recipient, maximum amount, token allowance, and transaction lifetime. - Monitor package ownership and release events, and establish a revocation process for compromised releases.