T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:68- Finding
Unverified Remote Installer Scripts Executed Directly
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 68–72
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 setup instructions download mutable scripts from an external server and immediately execute their contents through Bash or PowerShell. Neither command pins a release, verifies a cryptographic checksum or signature, nor provides an inspection step before execution. Consequently, the effective code executed by the Skill can change after the reviewed
SKILL.mdfile has been published.The installer domain is consistent with the stated OOMOL CLI provider, and installation is only recommended when the
oocommand is unavailable. Nevertheless, directly executing an unverified network response exceeds the minimum privileges and trust required to explain how to install the connector. A compromised vendor server, distribution infrastructure, DNS/TLS path, or installer could convert this documented setup action into arbitrary local code execution.No evidence in the reviewed project establishes that the current remote scripts are malicious. The vulnerability is the unsafe execution mechanism and its dependence on mutable, remotely controlled content.
Attack Path
- The
ooCLI is absent, causing an Airtable operation to fail withoo: command not found. - The Agent or user follows the first-time setup instructions in
SKILL.md. - The command retrieves
install.shorinstall.ps1from the external OOMOL endpoint. - A compromised or maliciously modified endpoint returns attacker-controlled script content.
- Bash or PowerShell executes the response immediately, without integrity validation or prior review.
- The payload performs arbitrar ...[truncated 913 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Remove the
curl | bashandInvoke-RestMethod | Invoke-Expressioninstallation patterns. - Direct users to an official, authenticated package manager or a version-pinned release artifact.
- Download the installer or binary to a local file without executing it automatically.
- Publish and require verification of a cryptographic checksum and, preferably, a signature tied to a trusted release key.
- Present the resolved version, source URL, checksum, and intended changes before requesting explicit user approval.
- Execute the verified artifact with ordinary user privileges; request elevated privileges only for narrowly identified installation steps.
- Avoid automatic installation by the Agent. On a missing CLI, stop and provide safe manual installation guidance.
- Document the files, directories, network endpoints, and permissions used by the installer so users can evaluate its scope.
- Remove the
