T03 · Remote Payload Retrieval and Execution
Error
- Location
- SKILL.md:59
- Finding
- Unverified Remote Installer Scripts Executed Directly by System Shells## Vulnerability Details **File Location**: `SKILL.md`, lines 59–63 **Vulnerability Type**: Remote payload retrieval and execution **Risk Level**: Critical ```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 first-time setup instructions retrieve mutable scripts from `cli.oomol.com` and immediately execute the responses with Bash or PowerShell. Neither command pins a version, verifies a cryptographic checksum or signature, nor gives the user an opportunity to inspect the downloaded content before execution. HTTPS protects data in transit but does not guarantee that the current remote payload is the same payload that was reviewed. A compromised hosting service, publishing account, domain, certificate trust chain, or installer pipeline could therefore turn these installation commands into an arbitrary-code execution channel. Future changes made by the legitimate publisher would also execute without being covered by this audit. The behavior exceeds the minimum privileges needed to document or invoke the Gender-API connector because installing a CLI does not inherently require executing unverified, mutable network content directly in a shell. The project provides no local implementation or integrity metadata that constrains what these remote scripts can do. The Skill also directs the connector to transmit names, email addresses, and optional IP or caller-ID hints to an external service. That transfer is consistent with its declared Gender-API lookup functionality, and no evidence of covert exfiltration was found. Nevertheless, users should be informed before personal data is sent through OOMOL to Gender-API.com. ### Attack Path 1. The `oo` CLI is unavailable, causing the user or Agent to follow the first-time setup instructions. 2. An attacker compromises or gains control over the remote installer distributio ...[truncated 1205 chars]
- Remediation
- ## Remediation Suggestions 1. Remove both direct pipe-to-shell installation commands. 2. Prefer a trusted operating-system package manager or an official repository with package-signing verification. 3. Pin the CLI to a specific reviewed version rather than retrieving an unversioned installer. 4. If direct artifact installation is unavoidable: - Download the installer or binary to a local file without executing it. - Obtain its expected SHA-256 checksum from a separately secured source. - Verify a publisher signature and certificate identity where supported. - Abort installation if any integrity or authenticity check fails. - Allow the user to inspect the downloaded script before execution. - Execute it only after explicit user approval. 5. Document the expected publisher, destination paths, permissions, and system changes. 6. Do not request elevated privileges unless a specific installation operation requires them; prefer a user-scoped installation. 7. Inform users before transmitting names, email addresses, IP addresses, caller identifiers, or other personal data, and identify both OOMOL and Gender-API.com as network recipients or processors.