T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:60- Finding
Unverified Remote Installer Download and Immediate Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 60–64
Vulnerability Type: Remote payload retrieval and execution
Risk Level: HighThe first-time setup instructions execute mutable, remotely hosted installation scripts directly in a shell:
bash curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linuxpowershell irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShellTechnical Analysis
Both installation commands retrieve content from an external server and immediately pass it to a command interpreter. The fetched payload is not pinned to a reviewed version and is not authenticated using a cryptographic signature or verified against a trusted checksum before execution.
HTTPS protects the connection in transit but does not guarantee that the hosted script remains identical to the version reviewed during this audit. Compromise of the hosting infrastructure, publishing account, DNS configuration, or upstream deployment process could cause arbitrary attacker-controlled commands to be delivered.
Because the script is executed without first being saved and inspected, the effective code can change after the Skill has been reviewed. This exceeds the minimum privileges required to direct users to a CLI installation package: installation can instead use a versioned artifact with independent integrity verification.
Attack Path
- The
oocommand is unavailable, causing the documented first-time setup path to be used. - An attacker compromises or gains control over the remote installer endpoint or its deployment chain.
- The endpoint supplies a modified shell or PowerShell script containing attacker-controlled commands.
bashorieximmediately executes the downloaded response without integrity verification or user inspection.- The payload operates with the privileges of the user running the command and may perform further system actions.
...[truncated 697 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Remove direct
curl | bashandirm | iexinstallation instructions. - Distribute the CLI through a trusted package manager or a version-specific release artifact.
- Pin installation instructions to an explicit release version rather than a mutable installer URL.
- Require the artifact to be downloaded as a separate step.
- Publish cryptographic checksums or signatures through an independently protected channel and verify them before execution.
- Allow users to inspect the downloaded installer before running it.
- Require explicit user approval before installing software, and advise installation from a non-elevated account unless elevated privileges are strictly necessary.
- Document the expected files, permissions, network destinations, and system changes made by the installer.
- Remove direct
