T08 · Insecure Dependencies
Warning
- Location
- SKILL.md:52
- Finding
- Unpinned Global Installation of a Wallet-Authorized CLI Dependency<![CDATA[ ## Vulnerability Details **File Location**: `SKILL.md:52-62` and `SKILL.md:786-790` **Vulnerability Type**: Unpinned third-party executable dependency **Risk Level**: Medium ### Vulnerable Code ```bash bun install -g @bankr/cli ``` Or with npm: ```bash npm install -g @bankr/cli ``` The troubleshooting section repeats the unpinned installation: ```bash # Reinstall if needed bun install -g @bankr/cli ``` ### Technical Analysis The Skill directs users to globally install the latest version of `@bankr/cli` without specifying a reviewed version, lockfile, package integrity hash, or reproducible verification procedure. The installed CLI is subsequently entrusted with sensitive operations, including: - Receiving and storing Bankr API and LLM keys. - Sending authenticated requests to Bankr services. - Signing messages and structured data. - Submitting irreversible cryptocurrency transactions. - Writing configuration into Agent and development-tool configuration files. Global installation increases the potential impact because package lifecycle scripts and executable code run with the invoking user's permissions. Although the audit found no evidence that the named package is currently malicious, an upstream account compromise, malicious future release, or registry compromise could change the executable payload after the Skill itself has been reviewed. ### Attack Path 1. An attacker compromises the package publisher, registry account, or package distribution process. 2. The attacker publishes a malicious version under the existing `@bankr/cli` package name. 3. A user follows the Skill instructions and runs the unpinned global installation command. 4. The package executes locally with the user's privileges. 5. The malicious package reads Bankr credentials, modifies Agent configuration, alters transaction destinations, or captures transaction requests. 6. If the exposed key has Agent API write access, the attacker can invoke signing or transaction-s ...[truncated 789 chars]
- Remediation
- <![CDATA[ ## Remediation Suggestions 1. Pin the CLI to a specifically reviewed version, for example: ```bash npm install -g @bankr/cli@REVIEWED_VERSION ``` 2. Publish and verify the expected package integrity hash before installation. 3. Document the official package publisher, source repository, and release-signing process. 4. Prefer a project-local installation with a committed lockfile instead of global installation. 5. Disable or audit package lifecycle scripts where the package manager permits it. 6. Run the CLI under a dedicated, low-privilege operating-system account. 7. Use a dedicated Agent wallet with limited funds and a purpose-specific API key. 8. Require a security review before updating the pinned CLI version. ]]>