T03 · Remote Payload Retrieval and Execution
Note
- Location
- SKILL.md:60
- Finding
- Unverified Remote Installer Download and Immediate Shell Execution## Vulnerability Details **File Location**: `SKILL.md`, lines 60–64 **Vulnerability Type**: Remote payload retrieval and execution **Risk Level**: Malicious ### 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 scripts from `cli.oomol.com` and immediately execute the returned content using Bash or PowerShell. Neither command pins an immutable release, validates a cryptographic signature or checksum, nor saves the script for inspection before execution. HTTPS protects the script while it is in transit but does not establish that its contents are safe. A compromised vendor account, hosting platform, DNS or PKI infrastructure, or malicious future replacement of the installer could cause different code to execute after the Skill has been reviewed. Installing the `oo` CLI may be necessary when it is unavailable, but piping an unverified network response directly into a shell exceeds the minimum behavior necessary to perform that installation safely. The Skill does limit this instruction to first-time setup after a command-not-found error, but that condition does not mitigate the integrity risk. ### Attack Path 1. The user or Agent attempts to use the Skill on a system where the `oo` CLI is unavailable. 2. The first-time setup instructions are followed. 3. Bash or PowerShell retrieves the installer from `cli.oomol.com`. 4. The network response is passed directly to the local shell without integrity verification or review. 5. If the hosted installer or its delivery infrastructure has been compromised, attacker-controlled commands execute immediately with the permissions of the invoking user. 6. The payload can access resources available to that user and may download further components, alter user configuration, or establish persistence. ### Impact Ass ...[truncated 894 chars]
- Remediation
- ## Remediation Suggestions 1. Remove the `curl | bash` and `irm | iex` installation patterns. 2. Require explicit user approval before installing the CLI. 3. Prefer a trusted platform package manager with a pinned package version. 4. If a standalone installer is required: - Pin an immutable, versioned release URL. - Download the installer to a local file rather than executing the response stream. - Verify a vendor-published cryptographic signature or pinned SHA-256 digest. - Abort installation if verification fails. - Allow the user to inspect the downloaded installer before execution. 5. Execute the installer without administrative privileges unless a documented installation step strictly requires elevation. 6. Document the files, directories, environment settings, and permissions modified by installation. 7. Provide uninstall and rollback instructions. 8. Keep the existing behavior that installation occurs only after an actual command-not-found failure, rather than proactively installing software.