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: Highbash curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linuxpowershell irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShellTechnical Analysis
The setup instructions retrieve mutable scripts from an external server and pass them directly to Bash or PowerShell. Neither command pins an installer version, validates a cryptographic checksum or signature, nor gives the user an opportunity to inspect the downloaded content before execution.
Consequently, the code that ultimately runs is not contained in the audited Skill and can change after review. Although the download domain is consistent with the declared OOMOL integration and the instructions only recommend installation after a command-not-found error, direct remote-script execution exceeds the minimum privilege necessary to provide installation guidance.
The project does not contain evidence that the current remote installers are malicious. The vulnerability arises from delegating local code execution to mutable, unverified network content.
Attack Path
- The user or agent attempts to invoke
ooand receives anoo: command not founderror. - The agent follows the first-time setup instructions in
SKILL.md. - The installation script is retrieved from
cli.oomol.com. - An attacker who has compromised the hosting service, its deployment pipeline, or the relevant network trust path supplies modified script content.
- The shell executes that content immediately, without integrity validation or inspection.
- The payload can perform any operation permitted to the account running Bash or PowerShell.
Impact Assessment
Successful exploitation provides arbitrary code execution with the privileges of the invoking user. Depending on those privileges a ...[truncated 824 chars]
- The user or agent attempts to invoke
- Remediation
View remediation
Remediation Suggestions
- Remove the
curl | bashandirm | iexinstallation patterns. - Direct users to a version-pinned release artifact or a trusted platform package manager instead of executing a mutable installer endpoint.
- Require the installer to be downloaded as a file before execution.
- Publish an expected SHA-256 or stronger checksum through an independently protected release channel and verify it before running the artifact.
- Prefer signed packages and enforce signature verification against a documented publisher key.
- Require explicit user approval before installing software; the agent should not perform installation automatically after a failed command.
- Encourage execution without administrator or root privileges unless a documented installation step strictly requires elevation.
- If script-based installation remains necessary, pin an immutable installer version, display the exact source and destination to the user, and provide separate download, verification, inspection, and execution commands.
- Remove the
