Back to skill

Security audit

market-report-using-cmc-cli

Security checks for vulnerabilities and agentic risk

Overview

This skill is a disclosed CoinMarketCap CLI reporting helper with no bundled code, persistence, or hidden behavior, though its trigger wording and manifest formatting are somewhat loose.

Install only if you are comfortable providing a CoinMarketCap API key to the configured cmc CLI. Review ambiguous requests before running reports if you want to avoid unnecessary API calls, and note that malformed metadata may need cleanup for reliable installation.

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
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
Findings (1)

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The trigger list includes broad, natural-language phrases such as "how's crypto today" and "today's crypto market summary," which are common conversational requests and can cause the skill to activate when a user did not specifically intend to invoke this particular tool. In an agent environment, overbroad activation increases the chance of unintended command execution against the external cmc CLI and unnecessary use of the CMC_API_KEY, which can lead to noisy behavior, privacy concerns around user intent routing, and avoidable external API usage.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.