T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:62- Finding
Unverified Remote Installation Scripts Executed Directly by Shells
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 62–66
Vulnerability Type: Remote payload retrieval and immediate 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 URL and immediately execute them using
bashor PowerShell'sInvoke-Expression. The downloaded content is not pinned to a specific version or cryptographic digest, saved for inspection, or authenticated with a verifiable release signature.Although the hosting domain is consistent with the declared OOMOL integration, the effective code executed by these commands can change after the Skill has been reviewed. Compromise of the hosting infrastructure, DNS or TLS path, release process, or installer source would consequently provide a direct arbitrary-code-execution channel.
Installing the CLI is relevant to the Skill's functionality when it is absent, but automatic execution of unverified remote code exceeds the minimum privilege and trust required for installation.
Attack Path
- The
oocommand is unavailable, and the Agent follows the documented first-time setup procedure. - An attacker compromises or otherwise gains control over the remotely served installation script or its delivery chain.
- The
curl | bashorirm | iexpipeline downloads the attacker-controlled content. - The shell executes the content immediately, without integrity verification or an opportunity to inspect it.
- The payload performs arbitrary actions using the permissions of the user or process running the installer.
Impact Assessment
A malicious installer could read or modify files accessible to the executing account, steal locally available credentials, alter shell or ...[truncated 639 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Remove the
curl | bashandirm | iexinstallation patterns. - Prefer an official operating-system package repository or a version-pinned release artifact.
- Download the installer or binary to a local file without executing it immediately.
- Verify a vendor-published cryptographic signature or a SHA-256 digest obtained through an independently trusted channel.
- Display the exact version, source, destination, and requested privileges to the user and obtain explicit approval before installation.
- Execute the verified installer as a separate step using the least-privileged account possible.
- Avoid silent privilege elevation and document all files, services, and configuration that the installer may create.
- If scripted installation remains necessary, pin an immutable release URL and fail closed when signature or digest verification fails.
- Remove the
