T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:56- Finding
Unverified Remote Installation Scripts Executed Directly by Shells
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 56-60
Vulnerability Type: Remote payload retrieval and execution
Risk Level: HighThe first-time setup instructions provide direct download-to-execution commands for both Unix-like systems and Windows:
bash curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linuxpowershell irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShellTechnical Analysis
These commands retrieve mutable content from an external server and immediately execute it using
bashor PowerShell'sInvoke-Expression. The instructions do not pin a reviewed release, verify a cryptographic signature or hard-coded digest, save the payload for inspection, or obtain explicit approval immediately before execution.HTTPS protects the network connection in transit but does not guarantee that the delivered script is safe. Compromise of the vendor host, publishing pipeline, DNS infrastructure, certificate issuance process, or account controlling the hosted scripts could cause the same reviewed Skill instructions to execute a different payload later.
Installing the
ooCLI may support the declared BigPicture.io connector workflow, but executing an unverified remote script is not the minimum privilege or minimum-risk mechanism necessary to install it. The downloaded script receives all permissions held by the user or agent process.Attack Path
- The
oocommand is unavailable, causing the agent or user to follow the first-time setup instructions. - An attacker compromises the external script host, its deployment pipeline, or another component capable of controlling the response.
- The attacker replaces
install.shorinstall.ps1with malicious content. curl | bashorirm | iextransfers the response directly into a command interpreter without local verification.- The malicious commands execute with the permissions of th ...[truncated 1035 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Remove the
curl | bashandirm | iexinstallation commands. - Prefer a trusted operating-system package manager or an official package repository with a pinned CLI version.
- If direct download is necessary, download the installer to a local file without executing it.
- Pin the download to an immutable, reviewed release rather than a mutable generic installation URL.
- Publish and verify a cryptographic signature using a separately distributed, trusted public key.
- Verify a hard-coded SHA-256 or stronger digest before execution; do not retrieve the expected digest from the same mutable location as the installer.
- Allow the user to inspect the downloaded script and clearly disclose the files, permissions, and configuration it will modify.
- Require explicit user approval before executing installation code.
- Run installation with ordinary user privileges unless a specific operation demonstrably requires elevation, and isolate the process where practical.
- Fail closed if signature, digest, version, or origin validation does not succeed.
- Remove the
