Back to skill

Security audit

Resend

Security checks for vulnerabilities and agentic risk

Overview

Resend actions require user approval, but setup runs unverified downloaded software whose documented behavior includes installing additional agent skills.

Review and approve CLI setup separately before allowing automatic installation. Confirm that you trust OOMOL to handle your Resend connection and email data. Its current documentation provides OO_SKILLS_SYNC_DISABLED=1 to prevent startup skill-directory writes; configure that before running the CLI if those changes are unwanted. See the [documented control](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). Installer contents and the exact installed release 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
  • MCP Tool PoisoningHidden Instructions, Unicode Deception, Parameter Description Injection
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
Findings (4)

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
98% confidence
Finding

The supplied command performs remote script execution for an apparent Oomol CLI installation rather than a Resend operation. Nothing in the supplied chunk establishes that this installation supports the declared Resend functionality. The downloaded script's contents are not provided, so its further effects cannot be assessed.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
92% confidence
Finding

The supplied code only invokes an oo login command. It neither performs Resend operations nor establishes that this authentication supports Resend. Although authentication can be a supporting implementation detail, the provided chunk does not show that relationship, so its observed purpose differs from the declared Resend functionality.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
97% confidence
Finding

The setup command streams a remotely fetched script directly into Bash without a pinned version or independent integrity verification; the Windows alternative similarly executes downloaded content. If the installer endpoint or its publishing infrastructure is compromised, attacker-controlled code would execute with the invoking user's privileges, potentially exposing local data and credentials. The missing-CLI condition limits exposure but does not remove this supply-chain risk.

Content

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

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