T08 · Insecure Dependencies
- Location
SKILL.md:5- Finding
Unpinned Third-Party CLI Executes with Access to a Funded Wallet Private Key
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 5–11 and 31–34
Vulnerability Type: Unpinned third-party dependency with access to sensitive wallet credentials
Risk Level: HighVulnerable Code
yaml compatibility: Requires outbound HTTPS, Node 18+ for the reference CLI, and a dedicated wallet in WALLET_KEY holding at least $5 USDC (EVM 0x key or base58 Solana key). Never a main wallet. metadata: openclaw: emoji: "🏛️" primaryEnv: WALLET_KEY requires: env: - WALLET_KEYbash export WALLET_KEY=... # dedicated wallet, at least $5 USDC npx @deskcrew/board-runner create --name "My Research Desk" --save board.jsonThe same unpinned package is also invoked for financially consequential operations at lines 49–52 and 63–65:
bash export BOARD_API_KEY=... # from create npx @deskcrew/board-runner deposits # where to send USDC npx @deskcrew/board-runner claim --tx <hash> --network base # credit what you sent npx @deskcrew/board-runner post --subject "Best webhook retry strategy?" \ --body "Context and constraints." --reward 1bash npx @deskcrew/board-runner drafts # the competing answers npx @deskcrew/board-runner decide --draft 812 --approve # winner paid 85% npx @deskcrew/board-runner decide --draft 813 --reject --reason "Ignores the constraints."Technical Analysis
The Skill instructs users to execute
@deskcrew/board-runnerthroughnpxwithout specifying an exact package version or an integrity hash. Consequently, the code executed may be whichever package version the npm registry resolves at invocation time rather than a fixed artifact that was reviewed with the Skill.The spawned package can inherit
WALLET_KEY, which contains an EVM or Solana private key for a wallet holding spendable USDC. It also participates in operations that create and fund a board, discover deposit addresses, claim deposits, post paid tasks ...[truncated 1877 chars]- Remediation
View remediation
Remediation Suggestions
- Pin
@deskcrew/board-runnerto an exact, reviewed version in every command rather than allowing floating registry resolution. - Publish cryptographic checksums or signed release provenance and require verification before execution.
- Include the CLI source, manifest, and lockfile in the auditable Skill artifact so its transaction and secret-handling behavior can be reviewed.
- Prefer a locally installed, integrity-locked dependency over downloading executable code at invocation time.
- Do not expose a raw wallet private key directly to a third-party Node.js process. Use a hardware wallet, constrained signer, isolated signing service, or wallet interface requiring explicit confirmation.
- Apply wallet spending limits and avoid unlimited token approvals. Keep only the minimum amount required in the dedicated wallet.
- Require users to verify the network, token contract, recipient, amount, and calldata before authorizing each transaction.
- Isolate the CLI process, restrict outbound connectivity where feasible, and avoid passing unrelated secrets into its environment.
- Document a verified package version and a reproducible upgrade-review procedure for future releases.
- Pin
