T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:136
- Finding
- Unverified Remote Installer Retrieval and Execution## Vulnerability Details **File Location**: `SKILL.md`, lines 136–140 **Vulnerability Type**: Remote payload retrieval and execution **Risk Level**: Critical The first-time setup instructions execute remotely downloaded installer scripts directly in local command interpreters: ```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 commands retrieve mutable content from a remote endpoint and immediately execute it through Bash or PowerShell. The instructions provide no pinned release version, cryptographic signature verification, checksum validation, package-manager verification, or opportunity to inspect the downloaded script before execution. HTTPS protects data in transit but does not establish that the script itself is safe. If the hosting infrastructure, domain, deployment pipeline, or publisher account is compromised—or if the mutable installer is changed after this Skill is reviewed—the effective payload can become malicious without any modification to the audited project. The domains are consistent with the declared OOMOL service, and the audit found no evidence that they are unrelated attacker-controlled hosts. Nevertheless, direct remote-to-shell execution creates an unrestricted code-execution channel and exceeds the minimum privilege necessary to provide installation guidance. ### Attack Path 1. The `oo` command is unavailable, causing the user or Agent to follow the first-time setup instructions. 2. The host requests the current `install.sh` or `install.ps1` content from `cli.oomol.com`. 3. An attacker who has compromised the hosting service, publishing pipeline, domain, or installer replaces the expected script with a malicious payload. 4. The pipe sends the response directly to Bash, or `Invoke-Expression` evaluates the PowerShell response. 5. The malicio ...[truncated 934 chars]
- Remediation
- ## Remediation Suggestions 1. Remove the `curl | bash` and `Invoke-Expression` installation patterns. 2. Prefer installation through a trusted operating-system package manager or signed vendor package, with an explicitly pinned version. 3. If direct download is unavoidable: - Use an immutable, version-specific release URL. - Download the artifact to a local file without executing it. - Verify a separately published SHA-256 checksum and a cryptographic signature from a trusted signing key. - Present the verified file for inspection before executing it as a distinct step. 4. Keep CLI installation outside routine Skill execution and require explicit user approval before installing software. 5. Run the installer with the least-privileged account necessary and avoid administrator or root execution unless a documented installation step specifically requires it. 6. Document the files, directories, and permissions modified by the installer so users can assess its expected scope.