T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:69- Finding
Unverified Remote Installer Downloaded and Executed Directly
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 69–73
Vulnerability Type: Remote payload retrieval and execution
Risk Level: Criticalbash 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 pass them to Bash or PowerShell. They do not pin an installer version, validate a cryptographic checksum or publisher signature, save the script for inspection, or otherwise verify the downloaded payload before execution.The remote scripts are not included in the audited project, so their effective behavior cannot be determined from the artifact. Although the hostname is consistent with the declared OOMOL service and installation is presented as a conditional first-time setup step, direct pipe-to-interpreter execution is not required for the Skill's declared GTmetrix functionality. It expands the trust boundary from the reviewed Skill to mutable, externally hosted code.
Attack Path
- The
oocommand is unavailable on the user's system. - The Agent or user follows the first-time setup instructions in
SKILL.md. curlorInvoke-RestMethodretrieves an installer fromcli.oomol.com.- The response body is passed directly to Bash or PowerShell without integrity verification or review.
- If the hosting infrastructure, publishing process, DNS path, TLS endpoint, or installer content has been compromised, attacker-controlled commands execute locally.
- Those commands can perform any operation permitted to the account that launched the interpreter.
Impact Assessment
Exploitation provides arbitrary command execution with the privileges of the invoking user. The potential scope includes reading or modifying user-accessible files, stealing locally available crede ...[truncated 549 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Remove both pipe-to-interpreter installation commands from the Skill.
- Prefer installation through a trusted operating-system package manager or an official repository that verifies signed packages.
- Pin the CLI to an explicit reviewed version rather than retrieving an unversioned installer.
- If a standalone installer is necessary, download it to a local file first and do not execute it automatically.
- Publish expected SHA-256 hashes and verify the downloaded artifact before execution.
- Require a verifiable publisher signature in addition to a checksum, because checksums hosted alongside a compromised installer do not provide an independent trust boundary.
- Display the verified installer or its requested changes for review and obtain explicit user approval before execution.
- Run installation with ordinary user privileges unless a specific, documented operation requires elevation.
- Keep setup outside the normal Skill action path; the Skill should continue to assume that the CLI is preinstalled and should return a clear error when it is absent.
