T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:61- Finding
Unverified Remote Installer Download and Immediate Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 61–65
Vulnerability Type: Remote payload retrieval and execution
Risk Level: CriticalVulnerable Code
bash curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linuxpowershell irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShellTechnical Analysis
The installation instructions retrieve mutable scripts from external URLs and immediately execute them using
bashor PowerShell'sInvoke-Expression. Neither path pins an immutable release, verifies a cryptographic checksum or signature, nor gives the user an opportunity to inspect the downloaded script before execution.HTTPS provides transport protection and server authentication, but it does not ensure that the installer remains unchanged after the Skill has been reviewed. If the distribution server, DNS resolution, TLS termination infrastructure, hosting account, or release pipeline is compromised, an attacker can replace the installer with arbitrary code.
The behavior is presented as a fallback for first-time setup rather than an operation required for each Klaviyo request. Installing the CLI may be necessary to use the Skill, but direct execution of unverified remote content exceeds the minimum privilege and trust necessary to perform that installation safely.
Attack Path
- The
oocommand is unavailable, causing the user or agent to follow the first-time setup instructions. curlorInvoke-RestMethodrequests the current installer fromcli.oomol.com.- The remote installer has been maliciously replaced or modified through a compromise of the hosting or delivery infrastructure.
- The downloaded response is passed directly to
bashorInvoke-Expressionwithout local review or integrity verification. - The malicious payload executes with the privileges of the user running the command.
- The payload can access resources available to that user and may downlo ...[truncated 1138 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Remove direct
curl | bashandInvoke-RestMethod | Invoke-Expressionexecution patterns. - Pin installation instructions to a specific reviewed CLI version rather than a mutable installer endpoint.
- Download the installer or release artifact to a local file before execution.
- Publish and verify a cryptographic checksum or, preferably, a signed release artifact using a documented trusted signing key.
- Display the source URL, selected version, destination path, and expected integrity value before installation.
- Require explicit user approval before executing any downloaded installer.
- Prefer a reputable platform package manager where packages are version-pinned and integrity-verified.
- Run installation with ordinary user privileges unless elevation is demonstrably required; never recommend routine execution as root or administrator.
- Document what the installer changes, including installed files, environment modifications, telemetry, update mechanisms, and any persistence components.
- Clearly disclose that Klaviyo request data is processed through OOMOL and provide relevant privacy, retention, and access-control documentation.
A safer installation pattern is:
bash curl -fL -o oo-installer.sh \ "https://cli.oomol.com/releases/<PINNED_VERSION>/install.sh" echo "<EXPECTED_SHA256> oo-installer.sh" | sha256sum --check less oo-installer.sh bash oo-installer.shThe release URL and checksum must be immutable and obtained through a trusted, authenticated publication channel.
- Remove direct
