T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:56
- Finding
- Unverified Remote Installer Download and Immediate Execution## Vulnerability Details **File Location**: `SKILL.md`, lines 56–60 **Vulnerability Type**: Remote Payload Retrieval and Execution **Risk Level**: High ### Vulnerable Code ```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 retrieve mutable scripts from an external server and execute them immediately using Bash or PowerShell. They do not pin an installer version, validate a cryptographic checksum or signature, or provide an opportunity to inspect the downloaded content before execution. Installing the `oo` CLI is related to the Skill's declared purpose, and the scripts are hosted on the documented OOMOL domain. However, piping remotely retrieved content directly into a command interpreter is not the minimum safe privilege or trust model necessary to install a client. The effective installer payload is controlled outside the audited package and can change after review. The audit cannot establish that the current remote scripts are malicious because their contents were not included in the project. The confirmed vulnerability is the unsafe remote execution mechanism and its supply-chain exposure. ### Attack Path 1. The `oo` CLI is absent, causing an `oo: command not found` error. 2. The user or Agent follows the first-time setup instructions. 3. `curl` or `Invoke-RestMethod` retrieves the current installer from `cli.oomol.com`. 4. Bash or `Invoke-Expression` executes the response without integrity verification. 5. If the hosting infrastructure, publication pipeline, domain, TLS trust path, or installer itself has been compromised, attacker-controlled commands execute with the invoking user's privileges. ### Impact Assessment A substituted installer could run arbitrary commands as the current user. Depending on that user's permissions ...[truncated 360 chars]
- Remediation
- ## Remediation Suggestions - Replace direct `curl | bash` and `irm | iex` execution with a documented download-and-verify workflow. - Distribute a version-pinned release artifact through a trusted package manager or immutable release URL. - Publish a cryptographic checksum and preferably a verifiable signature for each installer artifact. - Download the installer to a local file, verify its expected origin, hash, and signature, and only then execute it. - Avoid requiring administrator privileges unless a specific installation operation needs them; clearly document any such operation. - Pin the installed CLI version and document a controlled update process so installer behavior cannot change silently after the Skill is audited. - Advise users to inspect the installer and run it in a restricted environment where practical.