T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:59- Finding
Remote Installer Downloaded and Executed Without Integrity Verification
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 59–63
Vulnerability Type: Remote payload retrieval and execution
Risk Level: CriticalThe first-time setup instructions execute mutable remote content directly in a local 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 scripts from an external server and immediately pass the responses to Bash or PowerShell. The instructions do not pin a version, verify a cryptographic signature or checksum, save the scripts for inspection, or confirm their contents before execution.
HTTPS provides transport protection but does not establish that the script remains identical to the version assessed during this audit. Compromise of the vendor server, publishing account, delivery infrastructure, or installer-generation process could change the effective payload after review.
Installing the
ooCLI may be necessary when it is absent, and the document limits this instruction to first-time setup following a command failure. Nevertheless, direct network-to-shell execution exceeds the minimum safe mechanism needed to install the dependency.Attack Path
- The user or agent attempts to use the Skill and discovers that the
oocommand is unavailable. - The setup instructions direct it to execute the applicable Bash or PowerShell command.
- The command retrieves a mutable installer from
cli.oomol.com. - An attacker who has compromised the remote installer or its delivery infrastructure substitutes attacker-controlled script content.
- Bash or PowerShell executes the response without integrity verification or review.
- The substituted script performs arbitrary actions under the privileges of the invoking process.
Impact Assessment
A compromised installer could ...[truncated 881 chars]
- The user or agent attempts to use the Skill and discovers that the
- Remediation
View remediation
Remediation Suggestions
- Replace network-to-shell pipelines with a version-pinned package or release artifact from an authenticated official distribution channel.
- Publish cryptographic checksums and preferably signed release manifests. Verify both the signature and checksum before executing or installing the artifact.
- Download the installer to a local file rather than piping it directly into a shell.
- Display the artifact source, pinned version, expected digest, and intended filesystem or permission changes before installation.
- Require explicit user approval before executing the downloaded installer.
- Run installation with ordinary user privileges unless elevated privileges are strictly required for a documented operation.
- Provide reproducible manual installation steps as a safer alternative.
- If bootstrap scripts must remain available, pin them to an immutable release and document an independent verification procedure.
