T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:56- Finding
Unverified Remote Installer Scripts Executed Directly by the Shell
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 56-60
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 download installer scripts from an external URL and immediately execute them using Bash or PowerShell. The scripts are not pinned to a specific immutable release, downloaded for inspection, or verified using a cryptographic signature or trusted checksum.
Although installing the OOMOL CLI is relevant when the required command is unavailable, direct pipe-to-shell execution is not the minimum safe mechanism needed to perform that installation. The effective code can change after the Skill has been audited. Consequently, the security of the local environment depends on the continued integrity of the remote domain, hosting infrastructure, DNS and TLS path, and publisher account.
No evidence establishes that the current remote scripts are malicious. However, this installation mechanism creates a remote code-execution channel that could deliver arbitrary code if the distribution infrastructure or installer were compromised.
Attack Path
- The
oocommand is unavailable, causing the documented first-time setup procedure to be used. - An agent or user runs the supplied macOS/Linux or Windows installation command.
- The command retrieves a mutable script from
cli.oomol.com. - Bash or PowerShell executes the response without prior inspection or integrity verification.
- A compromised or malicious response executes with the privileges of the invoking user.
- The payload could access that user's files and processes, steal credentials available to the process, modify user configuration, install additional software, or ...[truncated 800 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Remove the direct
curl | bashandirm | iexinstallation commands. - Pin installation instructions to a specific, immutable CLI release rather than a mutable installer endpoint.
- Download the release artifact to a local file without executing it immediately.
- Publish and require verification of a cryptographic signature or SHA-256 checksum over the downloaded artifact.
- Use a trusted platform package manager or signed operating-system package where available.
- Display the resolved version, source URL, expected checksum, and intended installation destination before installation.
- Require explicit user approval before downloading or executing installation code.
- Run installation without administrative privileges unless elevation is demonstrably required, and document any files or settings the installer changes.
- If an installer script remains necessary, provide a reviewable versioned script from an immutable release and execute the verified local copy as a separate step.
- Remove the direct
