T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:58- Finding
Unverified Remote Installer Retrieval and Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 58–62
Vulnerability Type: Remote payload retrieval and immediate 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 execute the responses immediately using Bash or PowerShell. Neither command pins the installer to a specific version or immutable artifact. The instructions also provide no checksum validation, digital-signature verification, or opportunity to inspect the downloaded content before execution.Although the remote domain is consistent with the stated OOMOL service, this does not eliminate the security risk. Compromise of the hosting infrastructure, CDN, DNS resolution, TLS termination, deployment account, or installer itself could cause arbitrary attacker-controlled commands to be returned and executed. PowerShell's
iexpresents the same underlying risk as piping acurlresponse into Bash.This installation behavior is not necessary during ordinary Serply search operations. It is presented only as a first-time fallback when
oois unavailable, but it expands the trust and privilege boundary beyond the Skill's declaredBash(oo *)runtime access. The audit found no evidence that the currently hosted scripts are malicious; the vulnerability is the unverified and mutable remote-code execution mechanism.Attack Path
- The user or agent attempts to use the Skill on a system where the
ooCLI is not installed. - Following the documented setup procedure, the user runs the Bash or PowerShell installation command.
- The command downloads a mutable script from
cli.oomol.com. - An attacker who has compromised the script, hosting account, delivery infrastructure, or relevant networ ...[truncated 1040 chars]
- The user or agent attempts to use the Skill on a system where the
- Remediation
View remediation
Remediation Suggestions
- Replace the pipe-to-shell and
iexinstructions with installation through a trusted operating-system package manager where possible. - Otherwise, link to a version-pinned release artifact hosted at an immutable location rather than a mutable generic installer URL.
- Publish a cryptographic checksum and a verifiable digital signature for every installer artifact.
- Require users to download the artifact to disk, verify its checksum and signature, and inspect it before execution.
- Document the installer's expected files, permission requirements, network connections, and system changes.
- Require explicit user approval before installation and prohibit agents from automatically executing setup commands.
- Run installation with ordinary user privileges unless a narrowly defined operation genuinely requires elevation.
- Prefer a command sequence such as download, signature verification, checksum verification, and explicit execution rather than directly connecting a network response to a command interpreter.
- Replace the pipe-to-shell and
