T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:61
- Finding
- Unverified Remote Installer Scripts Executed Directly by Shell Interpreters## Vulnerability Details **File Location**: `SKILL.md`, lines 61–65 **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 installation instructions download mutable content from an external server and pass it directly to a command interpreter. The Unix command executes the response using Bash, while the Windows command uses PowerShell's `Invoke-Expression`. The payload is not pinned to a specific version and is not verified using a cryptographic signature or an independently published checksum. HTTPS provides transport protection but cannot ensure that the server, publishing account, or hosted installer remains trustworthy. It also cannot prevent the remote owner from changing the effective payload after this Skill has been reviewed. Installing the CLI is only conditionally relevant when `oo` is unavailable. Arbitrary remote script execution is not the minimum privilege necessary to perform ordinary read-only Nasdaq queries. ### Attack Path 1. The `oo` command is unavailable, causing the user or Agent to consult the first-time setup instructions. 2. An attacker compromises the installer host, its publishing infrastructure, or another component capable of controlling the returned script. Alternatively, the remote publisher changes the script after the Skill audit. 3. The victim runs the documented `curl | bash` or `irm | iex` command. 4. The interpreter executes the response immediately, without an opportunity to inspect or verify the downloaded artifact. 5. The payload performs arbitrary actions under the privileges of the invoking account. ### Impact Assessment A malicious installer can obtain the full effective privileges of the user who executes it. Potentia ...[truncated 740 chars]
- Remediation
- ## Remediation Suggestions 1. Remove all pipe-to-interpreter installation commands, including both `curl | bash` and `irm | iex`. 2. Prefer installation through a trusted operating-system package manager with version pinning and package-signature validation. 3. If standalone installers are necessary: - Pin downloads to a specific immutable CLI version. - Download the installer to disk rather than executing the network response. - Publish SHA-256 or stronger checksums through an independent trusted channel. - Verify a cryptographic signature or checksum before execution. - Display the exact artifact and requested actions to the user. - Require explicit user approval before running it. 4. Execute installation with ordinary user privileges unless a documented component strictly requires elevation. 5. Document the files, directories, network endpoints, and configuration changes made by the installer. 6. Keep normal Skill operation limited to the declared `Bash(oo *)` capability and do not automatically trigger installation after a command failure. 7. Clearly disclose that Nasdaq query parameters are transmitted through OOMOL's connector infrastructure and avoid sending unrelated local data.