T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:61- Finding
Unverified Remote Installer Download and Immediate Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 61–65
Vulnerability Type: Remote payload retrieval and execution
Risk Level: HighThe first-time setup instructions execute remotely hosted installation scripts 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 combine remote content retrieval with immediate execution. The downloaded scripts are mutable and are not pinned to a specific release, inspected before execution, or validated using a cryptographic checksum or digital signature.
Although the scripts are hosted on a domain associated with the declared OOMOL service, the repository contents do not establish the integrity or future trustworthiness of the remote payload. A compromise of the hosting account, deployment pipeline, domain, DNS resolution, or TLS termination infrastructure could change the executed code after this Skill has been reviewed.
Installing the CLI may be necessary for the Skill's declared functionality, but executing an unverified remote script is not the minimum-privilege installation method. The script receives all permissions of the user running the shell and is not shown to be sandboxed or otherwise constrained.
The Skill also sends translation payloads to the OOMOL connector. That transmission is disclosed and functionally consistent with its cloud translation purpose; the reviewed file does not demonstrate unrelated data exfiltration or credential harvesting.
Attack Path
- An attacker compromises the remote installer hosting environment, publication pipeline, domain infrastructure, or another component capable of modifying the installer response.
- The attacker replaces either
install.shorinstall.ps1with a malicious payload. - A user encounters the docu ...[truncated 940 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the direct
curl | bashandirm | iexinstallation patterns. - Prefer a trusted platform package manager or a version-pinned release artifact from the official project repository.
- Download the installer to a local file without executing it automatically.
- Publish SHA-256 checksums and, preferably, cryptographic signatures through an independently protected release channel.
- Verify the checksum and signature before execution, and fail closed if validation does not succeed.
- Give the user an opportunity to inspect the downloaded installer and require explicit approval before running it.
- Pin documentation to an immutable CLI version rather than a mutable generic installer URL.
- Run installation with ordinary user privileges unless a narrowly defined operation genuinely requires elevation.
- Document the files, environment changes, network endpoints, and permissions used by the installer.
- Where practical, advise users to install the CLI independently rather than allowing an Agent to retrieve and execute installation code.
- Remove the direct
