Back to skill

Security audit

ChainKeep

Security checks for vulnerabilities and agentic risk

Overview

The skill clearly discloses its permanent, paid storage behavior and requires user approval, with precautions needed for the CLI and recovery keys.

Review and pin the CLI version before providing secrets. Use only a minimally funded dedicated wallet, protect recovery keys from command history and tool logs, and upload only files you accept storing permanently. Publisher documentation and package contents could not be independently retrieved during this review.

Vulnerability Patterns
  • Skill Instruction HijackingAlters the agent's session goals or safety constraints when the skill loads
  • Agent Memory PoisoningWrites attacker-controlled rules into memory that affect later sessions
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Vulnerability Patterns
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (5)

MCP server referenced without pinned version: 'npx -y chainkeep'.

Medium
Category
MCP Rug Pull
Confidence
98% confidence
Finding

Although this is a CLI rather than an MCP server, the unpinned npx -y chainkeep command can download and execute a changing npm release without an installation confirmation. Even the quote operation runs package code with access to the exported wallet private key and local files, so a compromised release could steal funds or data despite the command's stated nonpayment behavior.

Content

No source excerpt is available for this finding.

MCP server referenced without pinned version: 'npx -y chainkeep'.

Medium
Category
MCP Rug Pull
Confidence
98% confidence
Finding

The storage command executes an unpinned npm package while providing access to the wallet key, source file, and potentially generated encryption keys. A compromised release could bypass its own price-limit and approval checks, misuse the wallet, or publish sensitive plaintext permanently; the documented safeguards do not constrain malicious package code.

Content

No source excerpt is available for this finding.

MCP server referenced without pinned version: 'npx -y chainkeep'.

Medium
Category
MCP Rug Pull
Confidence
98% confidence
Finding

The retrieval command runs a mutable npm release and supplies the recovery key to that code. A compromised package could exfiltrate the key and decrypted content, as well as the wallet private key inherited from the documented environment; permanent availability of the encrypted file increases the consequences of recovery-key disclosure.

Content

No source excerpt is available for this finding.

MCP server referenced without pinned version: 'npx -y chainkeep'.

Medium
Category
MCP Rug Pull
Confidence
98% confidence
Finding

Listing files still executes the unpinned package with the permissions and environment of the agent. The read-only intent of this operation does not prevent a compromised npm release from accessing the exported wallet key, stealing funds, or reading unrelated local data.

Content

No source excerpt is available for this finding.

MCP server referenced without pinned version: 'npx -y chainkeep'.

Medium
Category
MCP Rug Pull
Confidence
98% confidence
Finding

This repeated retrieval example also resolves and executes an unpinned npm package, exposing supplied recovery keys and retrieved plaintext to any compromised release. Although the static finding incorrectly calls it an MCP server, the underlying supply-chain execution risk is real and especially consequential for permanently stored private files.

Content

No source excerpt is available for this finding.