T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:63- Finding
Unverified Remote Installer Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:63-72
Vulnerability Type:T03: Remote Payload Retrieval and Execution
Risk Level: CriticalThe first-time setup instructions execute mutable installation scripts retrieved from external URLs:
bash curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linuxpowershell irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShellTechnical Analysis
Both commands pass remotely retrieved content directly to a command interpreter. The instructions do not pin a release, verify a checksum or cryptographic signature, or provide an opportunity to inspect the downloaded script before execution.
HTTPS authenticates and protects the network connection under normal conditions, but it does not ensure that the publisher's infrastructure, deployment pipeline, DNS, or current installer content has not been compromised. Because the effective code can change after this Skill has been reviewed, the package itself does not define or constrain the code that will execute.
Installing executable software is also broader than the minimum privileges required to invoke an already-installed Buttondown connector. Although installation is presented as a conditional fallback when
oois unavailable, the fallback permits arbitrary code execution with the privileges of the user running the shell.Attack Path
- An attacker compromises the installer hosting infrastructure, release pipeline, DNS resolution, or the published installer itself.
- The Agent attempts to use the Skill on a system where the
ooCLI is not installed. - After the command-not-found error, the Agent follows the documented first-time setup procedure.
curlor PowerShell retrieves the attacker-controlled response.- The pipe passes that response directly to Bash or
Invoke-Expression. - The payload executes with the current user's privileges without integrit ...[truncated 916 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove all pipe-to-shell and download-to-
Invoke-Expressioninstallation commands. - Direct users to a versioned release artifact hosted through the vendor's documented release channel.
- Pin the expected CLI version rather than retrieving an unbounded latest installer.
- Publish and verify a SHA-256 checksum and, preferably, a cryptographic signature whose trusted public key is distributed independently.
- Download the artifact to disk first, validate its origin and integrity, and only then execute or install it.
- Require explicit user approval before installing software or making system-level changes.
- Prefer a trusted platform package manager with signed, versioned packages where available.
- Document the installer’s expected file-system changes, required permissions, and network destinations so users can assess its scope before installation.
- Remove all pipe-to-shell and download-to-
