Back to skill

Security audit

Massive (Polygon.io)

Security checks for vulnerabilities and agentic risk

Overview

The market-data functions fit the stated purpose, but setup executes downloaded code and leaves broader changes to your agent environment insufficiently controlled.

Review the CLI separately and approve its installation before allowing setup. Prefer a pinned, verified release. The publisher documents OO_SKILLS_SYNC_DISABLED=1 to prevent startup skill synchronization; see its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). Connect only the intended account and consider OOMOL credit costs. The remote installers and hosted implementation were not inspected or executed, so their precise effects 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 (4)

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
98% confidence
Finding

The supplied command performs remote software installation, not Massive data searching or reading. Nothing in the provided chunk establishes that this installer is a necessary supporting implementation detail for the declared purpose. The downloaded script's contents and any further effects are not visible.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

Piping a mutable remote script directly into Bash executes its contents with the agent process's local privileges, without a review or artifact-verification step. Compromise of the installation endpoint or its delivery infrastructure could expose accessible files and credentials or enable persistent system changes; HTTPS alone does not protect against a compromised publisher. The PowerShell installation alternative has the same underlying risk.

Content

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

The setup workflow executes downloaded installer scripts without warning about remote code execution or system changes.

Medium
Category
Output Handling
Confidence
96% confidence
Finding

The missing-CLI fallback directs an agent to execute remote installation code without explaining its system effects or requiring explicit installation approval. This escalates a read-only market-data task into local code execution; limiting setup to a missing dependency reduces exposure but does not establish authorization for that escalation.

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 115)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