T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:270
- Finding
- Unverified Remote Installer Scripts Executed Directly by Shells## Vulnerability Details **File Location**: `SKILL.md`, lines 270-278 **Vulnerability Type**: Remote payload retrieval and execution **Risk Level**: High The first-time setup instructions execute mutable scripts downloaded from an external service: ```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 Both installation commands pass an external HTTP response directly to a command interpreter. The downloaded content is not pinned to a reviewed version and is not subject to checksum, signature, or publisher verification before execution. Although `cli.oomol.com` is consistent with the declared OOMOL integration, the package contains no evidence that future responses from these URLs will be identical to the content reviewed during this audit. The effective executable payload can therefore change independently of the Skill. Compromise of the hosting infrastructure, installer publication process, domain, or delivery path could turn the documented setup operation into arbitrary local code execution. Installation of the required CLI may be legitimate when `oo` is unavailable, but direct script-to-shell execution exceeds the minimum privilege and trust necessary to install it safely. Downloading a fixed release, verifying it, and then performing an explicit installation would provide the required functionality without immediately interpreting an unverified network response. The Skill otherwise limits its declared tool access to `Bash(oo *)`. Its documented transfer of action payloads through `oo connector run` is intrinsic to the remote connector functionality, and the reviewed file contains no evidence of unrelated secret collection or credential-file exfiltration. ### Attack Path 1. The `oo` CLI is absent, causing an agent or user to follow the first-time setup instructions. 2. An ...[truncated 1249 chars]
- Remediation
- ## Remediation Suggestions 1. Remove the `curl | bash` and `irm | iex` installation patterns. 2. Direct users to a version-pinned release hosted in the CLI's verifiable official repository or package registry. 3. Download the installer or binary to a local file without executing it immediately. 4. Publish and verify a cryptographic checksum for the exact pinned artifact. Prefer a signed release and validate its signature against a documented publisher key. 5. Abort installation if checksum or signature verification fails. 6. Execute the verified artifact as a separate, explicit step using ordinary user privileges. 7. Document the files, network destinations, and permissions used by the installer so users can assess its effects before execution. 8. Avoid recommending elevated execution unless a specific installation operation requires it; isolate any privileged step from the downloaded installer logic. 9. Where possible, use a platform-native package manager with version pinning and package-signature verification.