Back to skill

Security audit

charter-compute

Security checks for vulnerabilities and agentic risk

Overview

ClawScan rates this skill suspicious because a scanner flagged an unpinned `npx -y charter-mcp` command that could run a future package release; the review was partial.

Consider the unpinned package command a real installation risk: a future release could differ from the one reviewed. Skillspector recommends using an exact reviewed version or an integrity-verified dependency and restricting the client’s access. The review is partial because some local references could not be resolved, so the available evidence does not establish that all risks were covered.

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
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
Findings (1)

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

Medium
Category
MCP Rug Pull
Confidence
99% confidence
Finding

The unversioned npx -y charter-mcp command downloads and executes the package's current default release without an approval prompt, allowing a compromised or malicious future release to execute with the agent's local permissions. This is especially consequential because the client has access to a locally stored wallet private key; a malicious release could steal that key or other accessible secrets and bypass the legitimate client's spending controls.

Content

No source excerpt is available for this finding.