Back to skill

Security audit

CoinMarketCal

Security checks for vulnerabilities and agentic risk

Overview

The skill reads CoinMarketCal data, but its setup can execute unverified downloaded code without clearly asking your permission.

Review and install the CLI separately before allowing agent use, and explicitly approve local software changes. Consider whether you trust OOMOL to handle your connected CoinMarketCal credentials and billing. Review automatic agent-skill changes; the documented synchronization control is OO_SKILLS_SYNC_DISABLED=1 in the [CLI reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). The remote installer contents remain unverified.

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
  • Excessive AgencyUnrestricted Tool Access, Autonomous Decision Making, Scope Creep
  • Output HandlingUnvalidated Output Injection, Cross-Context Output, Unbounded Output
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
Findings (5)

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
97% confidence
Finding

The supplied chunk performs remote script execution rather than searching or reading CoinMarketCal data. Although installation can be a supporting implementation detail, this chunk establishes no relationship between the Oomol installer and the declared purpose. The downloaded script is not supplied, so its additional behavior cannot be determined.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
96% confidence
Finding

The supplied code only invokes a login command. It contains no CoinMarketCal-specific operation or data retrieval, and nothing establishes that this authentication is a supporting step for CoinMarketCal access.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

Piping a live HTTPS response directly into bash executes whatever the remote endpoint returns, without pinning or independently verifying the installer. Compromise of the distribution endpoint could therefore execute attacker-controlled code with the agent process's privileges; this is the same underlying installation risk identified by SQP-2, not evidence that the endpoint is currently malicious.

Content

Scanner excerpt · SKILL.md (reported line 59)May include surrounding context.

The setup workflow executes remotely downloaded installer scripts without warning the user about the system-integrity implications.

Medium
Category
Output Handling
Confidence
96% confidence
Finding

The setup instructions direct the agent to execute downloaded shell or PowerShell code without an explicit approval gate or integrity verification. Although limited to a missing-CLI condition, this can turn a read-only data request into local system modification and potentially arbitrary code execution with the agent process's privileges.

Content

No source excerpt is available for this finding.

Autonomous Decision Making

Medium
Category
Excessive Agency
Confidence
80% confidence
Finding

Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.

Content

Scanner excerpt · SKILL.md (reported line 80)May include surrounding context.

md
- **`OOMOL_INSUFFICIENT_CREDIT`** — OOMOL billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.

- **HTTP 402 without `OOMOL_INSUFFICIENT_CREDIT`** — the third-party account itself has no active plan or credit. Report the provider error message as is; do not ask the user to recharge OOMOL.

## Resources