ClawHub
Back to skill

Security audit

Lemon Squeezy

Security checks for vulnerabilities and agentic risk

Overview

The skill is mostly coherent for managing Lemon Squeezy through OOMOL, but its setup instructions include direct execution of remote installer scripts and it can modify account data.

Review the setup path before installing. Prefer installing the OOMOL CLI from a verified, versioned source rather than piping a remote script directly into a shell. Use this skill only for intended Lemon Squeezy account work, and require explicit confirmation before creating, updating, or deleting customers or webhooks.

A.I.G

Vulnerability Patterns
  • Remote Payload Retrieval and ExecutionFetches external code whose behavior can change after review
  • 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
  • Embedded Malicious CodeShips malicious scripts inside the skill and executes them locally
  • Unauthorized Access and Privilege EscalationObtains permissions beyond the task's legitimate needs
Findings (1)

T03 · Remote Payload Retrieval and Execution

Error
Location
SKILL.md:70
Finding

Unverified Remote Installation Scripts Are Executed Directly by Shells

Content
View full analysis

Vulnerability Details

File Location: SKILL.md, lines 70–74
Vulnerability Type: Remote payload retrieval and execution
Risk Level: Critical

bash
curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux
powershell
irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell

Technical Analysis

The first-time setup instructions download mutable scripts from cli.oomol.com and immediately execute them using Bash or PowerShell. The instructions do not pin a release, verify a cryptographic checksum or publisher signature, or provide an inspection step before execution.

HTTPS protects the network connection under normal circumstances, but it does not establish payload immutability or protect users if the distribution server, DNS infrastructure, hosting account, certificate issuance process, or release pipeline is compromised. Because the retrieved content is not part of the audited project, its behavior can change after this Skill has been reviewed.

Installing the CLI is relevant when the required command is absent. However, direct pipe-to-shell execution exceeds the minimum privileges and trust required for installation. A versioned package or separately downloaded and verified artifact would provide the same functionality with a substantially smaller supply-chain risk.

Attack Path

  1. The oo command is unavailable, or an error leads the Agent to enter the documented first-time setup path.
  2. The Agent executes the command appropriate to the operating system.
  3. Bash or PowerShell retrieves the current script from the remote OOMOL endpoint.
  4. The downloaded response is passed directly to the local shell without integrity or authenticity verification.
  5. If the endpoint or delivery chain is compromised, attacker-controlled commands execute with the privileges of the user running the Agent.
  6. Those commands may access user-readable files and credentials, ...[truncated 758 chars]
Remediation
View remediation

Remediation Suggestions

  1. Remove both direct download-and-execute commands.
  2. Prefer a trusted operating-system package manager or an official package repository with package-signing enforcement.
  3. Pin the CLI to a specific reviewed version rather than retrieving an unversioned installation script.
  4. Download the artifact to a local file as a separate step and do not execute it automatically.
  5. Publish and verify a pinned SHA-256 checksum and, preferably, a cryptographic signature tied to a documented publisher key.
  6. Fail closed if signature or checksum verification fails.
  7. Allow the user to inspect and explicitly approve the downloaded installer before execution.
  8. Run installation without administrative privileges unless a narrowly defined installation step genuinely requires elevation.
  9. Document the files, permissions, and network endpoints used by the installer.
  10. Keep setup conditional on an actual missing-command error, and require explicit user confirmation before installing software.

SkillSpector

Vulnerability Patterns
  • Supply ChainUnpinned Dependencies, External Script Fetching, Obfuscated Code
  • Trigger AbuseOverly Broad Trigger, Shadow Command Trigger, Keyword Baiting Trigger
  • Prompt InjectionInstruction Override, Hidden Instructions, Exfiltration Commands
  • Data ExfiltrationExternal Transmission, Env Variable Harvesting, File System Enumeration
  • Privilege EscalationExcessive Permissions, Sudo/Root Execution, Credential Access
Findings (2)

External Script Fetching

High
Category
Supply Chain
Confidence
97% confidence
Finding

The skill instructs users to install software via a remote script piped directly into a shell, which executes network-fetched code without prior verification. If the install endpoint, transport path, or hosting account is compromised, this becomes an immediate arbitrary code execution vector on the user's machine.

Content

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

Vague Triggers

Medium
Category
Not specified by scanner
Confidence
95% confidence
Finding

The description says to use this skill for "ANY Lemon Squeezy request" and "Whenever a task involves Lemon Squeezy," which is a very broad activation condition. It does not provide constraints, exclusions, or negative examples, so ordinary mentions of Lemon Squeezy could trigger the skill unnecessarily.

Content

No source excerpt is available for this finding.

Static analysis

No suspicious patterns detected.