Back to skill

Security audit

Supadata

Security checks for vulnerabilities and agentic risk

Overview

The Supadata workflow fits its purpose, but its fallback setup automatically executes an unverified remote installer.

Review and verify the CLI installation separately before allowing this skill to run its fallback setup. Connect only the intended Supadata account and expect requests to pass through OOMOL and potentially consume credits. No malicious behavior was established; the concern is automatic execution of installer code outside the inspected package.

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
99% confidence
Finding

The supplied command installs or bootstraps external software rather than performing Supadata searches or reads. Nothing in the supplied chunk establishes this installer as a necessary supporting implementation detail. The remote script's contents are not supplied, so its further behavior cannot be determined.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
88% confidence
Finding

The supplied chunk performs only an authentication login operation; it contains no Supadata reference or data-search/read behavior. Authentication could support the declared purpose, but this chunk provides no evidence of that connection and instead implements a materially different immediate function.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
97% confidence
Finding

Piping an HTTPS response directly into Bash executes mutable remote content without a pinned version, signature verification, or review opportunity. If the installer endpoint or its publishing infrastructure is compromised, this could execute attacker-controlled code with the user's privileges; the legitimate dependency context does not eliminate that supply-chain risk.

Content

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

The setup workflow executes downloaded installation scripts without warning about the system-integrity implications.

Medium
Category
Output Handling
Confidence
93% confidence
Finding

The fallback setup directs the agent to execute downloaded shell or PowerShell scripts without an explicit approval or integrity-verification step. Unlike Supadata reads, installation can modify the local environment and execute with the invoking user's privileges; triggering it only when the CLI is missing limits exposure but does not remove this risk.

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