T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:58
- Finding
- Unverified Remote Installer Scripts Executed Directly by Shell Interpreters## Vulnerability Details **File Location**: `SKILL.md`, lines 58–62 **Vulnerability Type**: Remote payload retrieval and execution **Risk Level**: Critical The first-time setup instructions provide pipe-to-interpreter commands for both macOS/Linux and Windows: ```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 These commands retrieve mutable content from external URLs and execute it immediately with `bash` or PowerShell's `Invoke-Expression`. The instructions do not pin an installer version, verify a cryptographic checksum or signature, or provide an opportunity to inspect the downloaded content before execution. HTTPS protects the connection in transit but does not mitigate compromise of the hosting infrastructure, publishing account, DNS, certificate issuance process, or installer-generation pipeline. Because the effective script can change after this Skill has been audited, the reviewed package does not determine what code will ultimately execute. Installation is presented as a conditional fallback after an `oo: command not found` error rather than an action performed on every invocation. Nevertheless, software installation exceeds the minimum privileges needed to execute an already-installed connector and should require explicit user approval and artifact verification. ### Attack Path 1. The `oo` CLI is absent, or the agent encounters an error interpreted as `oo: command not found`. 2. The agent or user follows the documented first-time setup command. 3. The command downloads the current response from `cli.oomol.com`. 4. The response is passed directly to `bash` or `Invoke-Expression` without integrity validation or inspection. 5. If the remote source or delivery chain has been compromised, attacker-controlled commands execute with the privileges of the invoking pro ...[truncated 846 chars]
- Remediation
- ## Remediation Suggestions 1. Remove all direct `curl | bash` and `irm | iex` installation instructions. 2. Prefer a trusted operating-system package manager or a version-pinned release from an official, authenticated repository. 3. Download the installer as a file without executing it: ```bash curl --fail --location --output oo-install.sh "https://example.invalid/releases/vX.Y.Z/install.sh" ``` 4. Publish and verify a cryptographic signature or a SHA-256 checksum obtained through a separately protected release channel. 5. Allow the user to inspect the downloaded file before execution. 6. Require explicit user confirmation before installing software or executing any downloaded artifact. 7. Run the installer with the least-privileged account possible and avoid elevation unless a documented installation step strictly requires it. 8. Pin the CLI version and document expected files, permissions, network destinations, and installation effects. 9. For agent operation, report that the CLI is unavailable and provide safe setup guidance rather than automatically executing installation commands. 10. Treat OOMOL as a data-processing intermediary and disclose that Benchmark Email action payloads and returned contact information traverse its connector service. Limit requests to fields necessary for the user's task and do not include unrelated local data.