T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:74- Finding
Unverified Remote Installer Downloaded and Executed Directly
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 74–78
Vulnerability Type: Remote payload retrieval and execution
Risk Level: Highbash curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linuxpowershell irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShellTechnical Analysis
The first-time setup instructions pipe remotely retrieved content directly into
bashor PowerShell'sInvoke-Expression. Neither command pins an immutable installer version nor verifies a cryptographic signature or checksum before execution. Consequently, the code ultimately executed can differ from the content assessed during this audit.The URLs use HTTPS and appear consistent with the documented OOMOL service, and installation is presented only as a fallback when the CLI is unavailable. However, transport encryption alone does not establish the integrity or immutability of the installer. A compromised hosting service, publishing pipeline, domain, account, or TLS trust path could replace the installer with arbitrary commands.
This installation behavior is not necessary for the Skill's ordinary read-only World Cup data operations. The Skill can require the CLI as a prerequisite without automatically executing mutable remote code. It therefore exceeds the minimum privileges needed during normal Skill execution.
No evidence in the reviewed file proves that the current remote installer contains a malicious payload. The vulnerability is the unverified, mutable remote-code execution mechanism itself.
Attack Path
- The
oocommand is absent, causing an action to fail withoo: command not found. - An agent or user follows the first-time setup instructions in
SKILL.md. - The system retrieves
install.shorinstall.ps1from the remote OOMOL host. - The response body is passed directly to
bashorInvoke-Expressionwithout inspection, version pinning, signatur ...[truncated 1062 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Remove the direct
curl | bashandirm | iexinstallation commands. - Treat the
ooCLI as a documented prerequisite and require explicit user approval before installing software. - Prefer a trusted operating-system package manager or an official, versioned release repository.
- Pin the installer or binary to a specific immutable release instead of a mutable generic URL.
- Download the artifact to a local file without executing it:
- Use a destination with restrictive permissions.
- Reject redirects to unapproved domains.
- Inspect the downloaded artifact before execution.
- Verify a publisher-provided cryptographic signature or a SHA-256 checksum obtained through a separately authenticated channel.
- Execute the verified installer as a separate step and with the least-privileged account possible.
- Do not request administrator or root privileges unless a documented installation operation strictly requires them.
- Record and display the exact version, source URL, expected digest, and installation effects so users can make an informed decision.
- For managed environments, direct users to organization-approved software deployment procedures rather than performing installation from Skill instructions.
- Remove the direct
