Back to skill

Security audit

Yelp

Security checks for vulnerabilities and agentic risk

Overview

Review is warranted because setup executes unverified downloads and the linked CLI can install additional agent skills without disclosure here.

Review and install a verified CLI release yourself before use. Consider disabling startup skill synchronization with OO_SKILLS_SYNC_DISABLED=1, as described in the [CLI reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). Understand that OOMOL mediates Yelp access. The full bundled artifact was inspected, but the remote installer and exact downloaded release remain unverified; 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
  • 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
97% confidence
Finding

The supplied code performs no visible Yelp search or data-reading operation. Instead, it executes a third-party installer. Although dependency installation can be a supporting implementation detail, this chunk establishes no relationship between the installer and the declared Yelp functionality. The downloaded script's contents and any further effects are not available for assessment.

Content

No source excerpt is available for this finding.

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
90% confidence
Finding

Authentication can be a supporting implementation detail, but the supplied chunk consists entirely of a login command with no demonstrated connection to Yelp or implementation of the declared functionality. As provided, its primary behavior does not match the description.

Content

No source excerpt is available for this finding.

External Script Fetching

High
Category
Supply Chain
Confidence
99% confidence
Finding

The setup instructions pipe a remotely fetched, unpinned script directly into Bash without verifying its contents or integrity; the PowerShell alternative has the same weakness. Compromise of the distribution endpoint could execute attacker-controlled code with the invoking account's privileges, exposing local files and credentials or enabling persistence. Restricting this to missing-CLI recovery reduces exposure but does not remove the supply-chain risk.

Content

Scanner excerpt · SKILL.md (reported line 57)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 78)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