T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:74- Finding
Unverified Remote Installer Download and Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 74–78
Vulnerability Type: Remote payload retrieval and execution
Risk Level: HighVulnerable Code
bash curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linuxpowershell irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShellTechnical Analysis
The installation instructions retrieve mutable scripts from
cli.oomol.comand immediately execute their contents using Bash or PowerShell. Neither command pins a specific installer version nor performs cryptographic signature or checksum verification. The user is also given no opportunity to inspect the downloaded content before execution.Although the download domain appears related to the declared OOMOL service, the repository contains no evidence establishing the integrity or future behavior of these remote scripts. The effective executable payload can change after the Skill has been reviewed. Compromise of the download domain, hosting infrastructure, DNS resolution, TLS termination, or installer publishing pipeline could therefore turn these instructions into an arbitrary-code delivery channel.
This installation behavior is only presented as a fallback when the
oocommand is unavailable. It is not required for ordinary connector operations and exceeds the minimum privileges needed for the Skill's declared read-only Modjo AI functionality.Attack Path
- A user or agent attempts to use the Skill on a system where the
ooCLI is unavailable. - The first-time setup instructions direct the user to run the applicable installation command.
- The command retrieves the current remote installer from
cli.oomol.com. - The response body is passed directly to Bash or PowerShell without integrity verification or review.
- If the remote delivery path or publishing infrastructure is compromised, attacker-controlled commands execute with the privile ...[truncated 909 chars]
- A user or agent attempts to use the Skill on a system where the
- Remediation
View remediation
Remediation Suggestions
- Remove direct
curl | bashandirm | iexinstallation patterns. - Prefer a trusted platform package manager or a version-pinned release from a verifiable official repository.
- Download the installer to a local file rather than piping it directly into a command interpreter.
- Publish and verify a cryptographic signature or strong checksum obtained through an independently protected channel.
- Allow the installer contents to be inspected before execution.
- Require explicit user approval before installing software or executing any downloaded script.
- Run installation with ordinary user privileges unless a documented operation strictly requires elevation.
- Document the exact release version, expected checksum, publisher identity, destination paths, and permissions required by the installer.
- Keep installation outside normal Skill execution. If the CLI is missing, report the condition and direct the user to independently verified installation documentation rather than executing the installer automatically.
- Remove direct
