T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:66- Finding
Unverified Remote Installer Scripts Executed Directly by Shells
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 66–70
Vulnerability Type: Remote payload retrieval and execution
Risk Level: CriticalVulnerable Code
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 mutable scripts from
cli.oomol.comand immediately execute the returned content with Bash or PowerShell. The instructions provide no pinned release version, checksum validation, cryptographic signature verification, or opportunity to inspect the downloaded content before execution.HTTPS protects the connection in transit but does not establish that the script remains safe if the hosting origin, publishing account, DNS configuration, or release process is compromised. The effective executable payload can also change after this Skill has been reviewed.
Installing the
ooCLI is relevant to the Skill's functionality when the command is missing. However, executing unverified network output directly is not the minimum-risk mechanism necessary to install that dependency. The Skill otherwise declares onlyBash(oo *)as its allowed tool scope, while these setup instructions invoke general-purpose shells capable of performing arbitrary operations.Attack Path
- A user attempts to use the Skill on a system where the
ooCLI is unavailable. - The resulting
oo: command not founderror directs the user to the first-time setup instructions. - The user runs one of the documented installation commands.
- The command retrieves a mutable script from
cli.oomol.com. - Bash or PowerShell executes the response without integrity or authenticity verification beyond HTTPS.
- If the remote origin or distribution process has been compromised, attacker-controlled commands execute with the privileges of the user run ...[truncated 760 chars]
- A user attempts to use the Skill on a system where the
- Remediation
View remediation
Remediation Suggestions
- Remove the direct
curl | bashandirm | iexinstallation commands. - Direct users to an official installation guide or package manager that supports version-pinned releases.
- Download the installer to a local file before execution so it can be inspected:
- Use a fixed HTTPS URL containing an immutable release version.
- Reject redirects to unapproved hosts.
- Verify a publisher-provided SHA-256 or stronger checksum.
- Prefer cryptographic signature verification against a pinned, documented signing key.
- Execute the installer only after verification succeeds.
- Require explicit user approval before installing software; the agent should not automatically execute first-time setup commands after a failed connector invocation.
- Run installation with ordinary user privileges whenever possible and clearly document whether any elevation is required.
- Publish reproducible installer sources and retain immutable release artifacts so the reviewed payload corresponds to the installed payload.
- Preserve the existing guidance that setup should occur only after a matching failure, but replace shell execution of network output with a verifiable installation process.
- Remove the direct
