T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:62- Finding
Unverified Remote Installer Download and Immediate Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 62–66
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
The installation instructions retrieve mutable scripts from an external server and immediately execute them through Bash or PowerShell. Neither command pins a release, verifies a cryptographic signature or checksum, nor gives the user an opportunity to inspect the downloaded content before execution.
The installer payload is not included in the audited project. Consequently, its effective behavior cannot be reviewed from this repository and can change after the Skill has passed review. Although the download domain appears related to the declared OOMOL CLI and installation is presented as a fallback when
oois unavailable, immediate pipe-to-shell execution is not the minimum privilege or safest mechanism required to install that CLI.The network operations used by
oo connector runotherwise align with the Skill's declared cloud-service functionality. No covert exfiltration endpoint or embedded credential-harvesting behavior was identified in the audited file.Attack Path
- The
ooCLI is absent, causing the first-time setup fallback to apply. - The user or Agent follows the documented installation command.
- The command downloads the current script from
cli.oomol.com. - Bash or PowerShell executes the response without integrity or authenticity verification beyond ordinary HTTPS transport.
- If the hosting server, publishing pipeline, DNS/TLS trust chain, or remote installer is compromised, attacker-controlled commands execute with the privileges of the invoking account.
- The malicious payload could then access data available to ...[truncated 748 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Remove the direct
curl | bashandirm | iexinstallation commands. - Prefer an official package manager that validates signed metadata and packages.
- Pin installation instructions to a specific, reviewed CLI version rather than a mutable latest installer.
- Download the artifact without executing it, then verify a vendor signature or a hard-coded SHA-256 checksum obtained through an independently trusted channel.
- Abort installation on any verification failure.
- Allow the user to inspect the downloaded artifact before installation.
- Run installation without administrative privileges unless a documented component strictly requires elevation.
- Publish reproducible release artifacts and signed checksums so the installed binary can be tied to reviewed source.
- If scripted installation remains necessary, store a pinned and reviewed installer in a versioned release, verify it before execution, and clearly disclose the files, permissions, and network access it requires.
- Remove the direct
