T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:57- Finding
Unverified Remote Installation Scripts Executed Directly by Shell
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 57–61
Vulnerability Type: Remote payload retrieval and execution
Risk Level: HighVulnerable 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 first-time setup instructions retrieve mutable scripts from external URLs and immediately execute them with Bash or PowerShell. There is no version pinning, checksum verification, digital-signature validation, local inspection step, or other mechanism that establishes the downloaded payload's integrity before execution.
The download host is consistent with the declared OOMOL service, and installing the required CLI is relevant when
oois unavailable. However, immediate execution of unverified network content exceeds the minimum privilege and trust necessary to document or install that dependency. The effective payload can change after this Skill has been reviewed.The Skill itself does not contain evidence that the scripts are malicious. Nevertheless, compromise of the hosting infrastructure, publishing process, domain, or delivery path could turn these commands into an arbitrary-code-execution channel.
Attack Path
- The
oocommand is unavailable, causing the Agent or user to follow the first-time setup instructions. - An attacker compromises the remote installation script, its hosting or publishing infrastructure, or another component of the delivery chain.
curlorirmdownloads the attacker-controlled script.- The pipeline passes the response directly to
bashoriexwithout integrity verification or review. - The malicious script executes with the privileges of the Agent or user who launched the command.
Impact Assessment
A compromised installation payload could execute arbitrary commands with the invoking accou ...[truncated 913 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Remove all direct
curl | bashandirm | iexinstallation instructions. - Prefer a trusted operating-system package manager or a version-pinned release artifact from the CLI's documented official distribution channel.
- Download the installer or binary to a local file without executing it automatically.
- Pin the expected release version and verify a publisher-provided cryptographic signature or SHA-256 checksum before execution.
- Display the exact artifact, source, version, and command to the user, and require explicit approval before installing software.
- Run installation with ordinary user privileges unless elevated privileges are demonstrably required. Do not request blanket administrator or root access.
- Document how users can inspect the downloaded installer and abort safely if verification fails.
- Where practical, distribute the required CLI through a reproducible and auditable packaging process rather than a mutable remote script.
- Remove all direct
