T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:56- Finding
Unverified Remote Installation Scripts Executed Directly by Shells
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 56–60
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
cli.oomol.comand immediately execute their contents using Bash or PowerShell. Neither command pins an immutable release, validates a cryptographic checksum or signature, nor gives the user an opportunity to inspect the downloaded script before execution.The domain is consistent with the declared OOMOL integration, but the project contains no local evidence that establishes the integrity of the remotely served scripts. The effective code can change after this Skill has been reviewed. Compromise of the hosting infrastructure, distribution pipeline, domain, or trusted TLS path could therefore turn these commands into an arbitrary code-execution channel.
Installing the required CLI may be necessary during first-time setup, but executing a mutable remote response directly in a shell exceeds the minimum privileges necessary. A pinned and cryptographically verified package can provide the same functionality without granting an unreviewed network response immediate shell execution.
Attack Path
- The
ooCLI is unavailable, causing the documented first-time setup fallback to apply. - An agent or user follows the installation command in
SKILL.md. - The command downloads the current contents of
install.shorinstall.ps1. - Bash or PowerShell executes the response immediately without integrity verification.
- If the remote source or delivery chain has been compromised, attacker-controlled commands run with the privileges of the invoking user.
- Those commands can modify accessi ...[truncated 808 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Remove the
curl | bashandirm | iexinstallation patterns. - Pin installation instructions to a specific CLI version and immutable release artifact.
- Publish an expected SHA-256 or stronger checksum and verify it locally before execution.
- Prefer signed packages distributed through trusted platform package managers.
- If a standalone script is unavoidable, download it to a local file, verify its signature or checksum, display its source and version, and require explicit user approval before execution.
- Run installation with ordinary user privileges unless a narrowly defined operation genuinely requires elevation.
- Document the expected filesystem and configuration changes made by the installer.
- Keep setup conditional on an actual missing-command error, as already stated in the Skill, rather than invoking installation proactively.
- Remove the
