T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:58- Finding
Unverified Remote Installer Scripts Are Executed Directly
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 58–62
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 first-time setup instructions download mutable scripts from
cli.oomol.comand immediately execute the responses with Bash or PowerShell. There is no pinned version, expected cryptographic hash, signature verification, or review step between retrieval and execution.The remote scripts are not included in the audited project, so their contents and effective behavior cannot be verified from the package. Even if the domain is operated by the declared service provider, compromise of its hosting infrastructure, publishing pipeline, DNS resolution, or TLS endpoint could replace the installer with arbitrary commands after this Skill has been reviewed.
Installation is presented as a fallback when the
oocommand is unavailable rather than as part of every invocation. Nevertheless, executing an opaque remote response is not the minimum privilege or safest mechanism required to install the CLI. The Windows instruction has the same security properties as the Unix pipeline.Attack Path
- The user or Agent attempts to invoke the Skill on a system where the
ooCLI is unavailable. - Following the documented fallback, it runs one of the installation commands.
- The system retrieves a mutable script from
cli.oomol.com. - The response body is passed directly to Bash or PowerShell without integrity or authenticity verification beyond transport security.
- If the remote distribution channel has been compromised, attacker-controlled commands execute with the privileges of the invoking user or Agent process.
Impact Assessment
A substituted ...[truncated 600 chars]
- The user or Agent attempts to invoke the Skill on a system where the
- Remediation
View remediation
Remediation Suggestions
- Remove both download-and-execute one-liners.
- Prefer a trusted platform package manager or a signed, versioned release artifact from a verifiable repository.
- Pin the installer or package to a specific version rather than retrieving a mutable generic URL.
- Publish an expected cryptographic digest and require verification before execution.
- Where supported, verify a detached signature against a documented, securely distributed signing key.
- Separate download, verification, inspection, and execution into distinct steps.
- Require explicit user approval before installing software or executing an installer.
- Run installation with ordinary user privileges unless a documented operation strictly requires elevation.
- Document the files, network endpoints, and system changes made by the installer.
