Back to skill

Security audit

MailerSend

Security checks for vulnerabilities and agentic risk

Overview

The MailerSend actions have clear safeguards, but fallback setup executes an unverified remote installer without an explicit approval step.

Review and approve CLI installation separately before allowing the fallback. Use a verified release and review its effects on other installed agent skills; upstream documents a synchronization opt-out in its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). Connecting MailerSend entrusts OOMOL with the authorized account access and processed email data. Keep permissions narrow and retain the required confirmation before sending email. The downloaded installer and exact CLI release were not verified; no malicious behavior was established.

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 code performs remote software installation rather than the declared MailerSend data operations. Nothing in the chunk establishes this installer as a supporting dependency for MailerSend. The downloaded script's contents are not supplied, so its additional behavior cannot be determined.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
96% confidence
Finding

Piping a remote installer directly into bash executes its contents without prior inspection, version pinning, or integrity verification. HTTPS protects transport but does not prevent a compromised publisher or distribution endpoint from serving malicious code, potentially exposing local files and credentials; the conditional setup path reduces exposure but does not eliminate the risk.

Content

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

The setup workflow instructs the agent to execute remotely downloaded installation scripts without warning about the system-integrity implications.

Medium
Category
Output Handling
Confidence
93% confidence
Finding

The fallback instructs the agent to execute downloaded shell or PowerShell scripts without an explicit installation approval step or artifact verification. Although this is legitimate dependency setup and only occurs when the CLI is missing, a compromised installer source could execute arbitrary code with the invoking user's privileges; this overlaps with SC2.

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