Google Ads

• Outcome: Review
• Latest audit: Nov 3, 2026 · 11:12 AM UTC
• Version: 1.0.6

Overview

Google Ads changes require your approval, but automatic setup executes unverified downloaded code and may install additional agent skills.

Review and install a verified CLI release yourself before enabling this skill, including its effects on other agent skills. Understand that OOMOL mediates access to your connected Google Ads account, and review every proposed campaign change or customer-list upload. The remote installer and hosted implementation remain unverified; no malicious behavior was established.

A.I.G

Vulnerability Patterns

• Skill Instruction Hijacking: Alters the agent's session goals or safety constraints when the skill loads
• Agent Memory Poisoning: Writes attacker-controlled rules into memory that affect later sessions
• Remote Payload Retrieval and Execution: Fetches external code whose behavior can change after review
• Embedded Malicious Code: Ships malicious scripts inside the skill and executes them locally
• Unauthorized Access and Privilege Escalation: Obtains permissions beyond the task's legitimate needs

SkillSpector

Vulnerability Patterns

• Supply Chain: Unpinned Dependencies, External Script Fetching, Obfuscated Code
• Excessive Agency: Unrestricted Tool Access, Autonomous Decision Making, Scope Creep
• MCP Tool Poisoning: Hidden Instructions, Unicode Deception, Parameter Description Injection
• Prompt Injection: Instruction Override, Hidden Instructions, Exfiltration Commands
• Data Exfiltration: External Transmission, Env Variable Harvesting, File System Enumeration

Findings (3)

Description-Behavior Mismatch

High

• Category: MCP Tool Poisoning
• Confidence: 97% confidence

Finding

The visible behavior is remote software installation rather than Google Ads management. Installing a dependency can be a supporting implementation detail, but the supplied chunk provides no evidence that this installer supports the declared functionality. The downloaded script's contents are unavailable, so its further behavior cannot be determined.

Content

No source excerpt is available for this finding.

External Script Fetching

High

• Category: Supply Chain
• Confidence: 98% confidence

Finding

The fallback installation command executes a mutable network response directly in a shell without a pinned version or independent integrity verification; the PowerShell alternative has the same weakness. Compromise of the installation endpoint or delivery pipeline could execute arbitrary code with the invoking user's permissions, exposing local files and credentials. The missing-CLI prerequisite limits when this happens, and the declared oo-only tool allowance may block direct execution, but neither makes the documented installation method safe.

Content

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

• oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

  bash

  curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux
  

  powershell

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