T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:63- Finding
Unverified Remote Installation Scripts Are Executed Directly
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 63–70
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 returned content using Bash or PowerShell. Neither command pins a script version, verifies a cryptographic signature or checksum, nor provides an inspection step before execution.Although installing the
ooCLI supports the Skill's declared Ninox functionality, direct download-and-execute behavior gives the remote server control over the code executed on the local system. The effective payload can change after the Skill has been reviewed. Compromise of the distribution server, associated CDN, DNS resolution, TLS termination infrastructure, or release process could therefore turn these installation commands into an arbitrary-code-execution channel.This behavior exceeds the minimum privileges necessary to document CLI installation because safer installation mechanisms can separate downloading, verification, and execution.
Attack Path
- The
ooCLI is absent, causing anoo: command not founderror. - The agent or user follows the first-time setup instructions in
SKILL.md. curlorInvoke-RestMethodretrieves a mutable installation script from the remote server.- The response is passed directly to Bash or
Invoke-Expressionwithout integrity verification or review. - If the upstream delivery path has been compromised, attacker-controlled commands execute with the privileges of the invoking account.
- Those commands can access data available to that account, alter local files, steal credentials, install additional paylo ...[truncated 646 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Remove both pipe-to-shell installation commands.
- Prefer an official operating-system package manager or a version-pinned release artifact.
- Download the installer to a local file rather than executing the network response directly.
- Publish a SHA-256 or stronger checksum through an independently protected channel and require verification before execution.
- Cryptographically sign release artifacts and document signature verification using a pinned signing identity.
- Pin the installer and CLI to a specific reviewed version instead of using a mutable generic URL.
- Instruct users to inspect the downloaded script before running it.
- Run installation with ordinary user privileges unless a narrowly defined step demonstrably requires elevation.
- Document the files, directories, network endpoints, and permissions used by the installer so users can assess its effects.
- If automated installation remains necessary, fail closed when integrity or signature verification cannot be completed.
