Back to skill

Security audit

ChartMogul

Security checks for vulnerabilities and agentic risk

Overview

The ChartMogul reads fit the stated purpose, but automatic setup executes unverified remote code and may make broader changes to agent skills.

Review and install a verified CLI release separately before using this skill. Consider disabling automatic skill synchronization with OO_SKILLS_SYNC_DISABLED=1, and confirm the connected account's access. The bundled instructions were fully inspected; remote installers and hosted connector implementation 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
96% confidence
Finding

The skill's read-oriented purpose expands into local software installation when the CLI is missing, using remotely supplied code without integrity verification or explicit user approval. Dependency setup is relevant to the skill and is conditional, which reduces suspicion of malicious intent, but a compromised installer could execute arbitrary commands with the invoking user's privileges.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
88% confidence
Finding

Authentication could support a ChartMogul integration, but the supplied chunk contains only a login command, with no ChartMogul targeting or data-access behavior. Its observable purpose therefore differs materially from the declared purpose.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

The command pipes a live HTTPS response directly into Bash, giving the installer arbitrary execution privileges under the current user without checking a pinned version, signature, or trusted checksum. HTTPS protects transport but does not protect against compromise of the distribution endpoint; the conditional setup context reduces exposure but does not eliminate this supply-chain risk.

Content

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

The setup workflow executes remote installation scripts without warning about their system-level effects.

Medium
Category
Output Handling
Confidence
94% confidence
Finding

The setup instructions authorize shell and PowerShell installers without explaining that they execute third-party code and may modify the local environment. Although installation is conditional on a missing prerequisite, it crosses from reading ChartMogul data into local code execution without a separate consent step.

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