T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:57- Finding
Unverified Remote Installation Scripts Executed Directly by Shells
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 57–61
Vulnerability Type: Remote payload retrieval and execution
Risk Level: CriticalComplete Code Snippet:
bash curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linuxpowershell irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShellTechnical Analysis
Both installation commands retrieve mutable content from
cli.oomol.comand immediately pass the response to a command interpreter. The downloaded scripts are not pinned to a version, inspected before execution, or verified using a cryptographic signature or expected digest.HTTPS protects data in transit under normal conditions, but it does not establish that the retrieved script is the same artifact that was reviewed. A compromised hosting server, publishing account, certificate trust chain, or upstream release process could alter the effective payload at any time.
Installing the required
ooCLI is related to the Skill's functionality, but executing an unverified remote response is not the minimum-privilege installation method. The scripts execute with all permissions available to the invoking Bash or PowerShell process. The Windows command has the same fundamental issue as the flaggedcurl | bashcommand becauseInvoke-RestMethodoutput is passed directly toInvoke-Expression.The audit found no evidence that the current remote scripts are malicious. The vulnerability is that their contents are external, mutable, and executed without verification.
Attack Path
- A user invokes the Skill for an Ambient Weather operation.
- The
oocommand is unavailable, causing the documented first-time setup path to be used. - The agent or user runs the applicable installation command.
- The command retrieves the current script from
cli.oomol.com. - Bash or PowerShell executes the response without checking its version, signature, ...[truncated 1198 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove both direct execution patterns:
curl ... | bashirm ... | iex
- Prefer an official operating-system package manager with publisher verification and a pinned package version.
- If standalone artifacts are necessary, download a versioned release to a local file without executing it.
- Publish and require verification of a cryptographic signature from a documented trusted key. At minimum, verify a SHA-256 digest pinned in the reviewed Skill rather than downloaded from the same location as the artifact.
- Abort installation if signature or digest verification fails.
- Allow inspection of the verified installer before execution and obtain explicit user approval.
- Run installation with ordinary user privileges unless a specific operation demonstrably requires elevation; do not request broad administrative access by default.
- Pin the installer and CLI to reviewed versions, and update the Skill only after reviewing new versions.
- Document the files, processes, and network endpoints affected by installation so users can assess the trust boundary and remove the CLI cleanly.
- Keep normal connector operations separate from installation. A missing CLI should produce a clear setup error rather than automatically executing downloaded code.
- Remove both direct execution patterns:
