Back to skill

Security audit

Square

Security checks for vulnerabilities and agentic risk

Overview

The Square workflow is coherent, but fallback setup executes unverified downloaded code without a clear installation approval step.

Review and explicitly approve a pinned, verified CLI installation before allowing setup. Understand that Square customer operations pass through OOMOL, and retain the required confirmation for writes. Only SKILL.md was bundled; the remote installer and connector runtime were not available for inspection.

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
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
  • 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
Findings (5)

Description-Behavior Mismatch

High
Category
MCP Tool Poisoning
Confidence
97% confidence
Finding

The only supplied behavior is fetching and executing an external installer, rather than interacting with Square. Dependency installation could be a supporting implementation detail, but nothing in this chunk establishes that the installer supports the declared Square functionality. The remote payload's downstream behavior cannot be determined from the supplied code.

Content

No source excerpt is available for this finding.

Credential Access

High
Category
Privilege Escalation
Confidence
70% confidence
Finding

Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Content

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

md
- `create_customer` — Create a Square customer profile. [write]
- `get_customer` — Retrieve one Square customer profile by ID.
- `list_customers` — List Square customer profiles with cursor pagination.
- `list_locations` — List Square seller locations for the connected access token.
- `search_customers` — Search Square customer profiles with supported Square filters.
- `update_customer` — Update a Square customer profile by ID. [write]

External Script Fetching

High
Category
Supply Chain
Confidence
98% confidence
Finding

Piping an HTTPS response directly into bash executes whatever the endpoint returns with the agent process's local permissions, without inspection or independent integrity verification. A compromised distribution endpoint could therefore compromise the local environment; the PowerShell installation example has the same risk, although there is no evidence that either endpoint is currently malicious.

Content

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

Setup instructs the agent to execute downloaded installation scripts without warning the user about remote code execution or system changes.

Medium
Category
Output Handling
Confidence
96% confidence
Finding

On a missing-command error, the skill directs the agent to execute a downloaded installer without first explaining its effects or obtaining installation approval. This expands a Square data task into local code execution and system modification; the conditional setup trigger reduces exposure but does not establish user consent.

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