T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:58- Finding
Unverified Remote Installation Scripts Executed Directly by Shells
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 58–62
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
cli.oomol.comand immediately execute their contents using Bash or PowerShell. Neither installation path pins a release version, verifies a cryptographic signature or checksum, nor gives the user an opportunity to inspect the downloaded payload before execution.HTTPS protects the connection in transit under normal conditions, but it does not establish that the remotely hosted script is immutable or safe. The effective code can change after the Skill has been reviewed. Compromise of the hosting infrastructure, domain, DNS resolution, TLS issuance path, deployment credentials, or installer publishing pipeline could therefore turn these commands into an arbitrary-code execution channel.
Installing the
ooCLI supports the declared Mailjet integration, but piping a download directly into a shell is not the minimum privilege or minimum-risk method necessary to perform that installation.Attack Path
- The
ooCLI is unavailable, causing the user or agent to follow the first-time setup instructions. - An attacker compromises or gains control over the remote installer delivery path, such as the hosting account, publishing pipeline, domain, DNS, or TLS infrastructure.
- The attacker replaces the installer response with malicious shell or PowerShell commands.
- The documented
curl | bashorirm | iexpipeline retrieves the modified content. - The local shell executes the content immediately without integrity verification or review.
- The payload performs arbitrary actions permitted b ...[truncated 834 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Remove both direct download-to-shell pipelines.
- Publish versioned, immutable CLI releases through an official release repository or trusted package manager.
- Pin the installation instructions to a specific reviewed release rather than a mutable installer endpoint.
- Download the installer or binary to a local file without executing it automatically.
- Verify a publisher-provided cryptographic signature. If signatures are unavailable, verify a SHA-256 digest obtained through a separately protected and version-specific channel.
- Display the source URL, selected version, destination, and expected changes before installation, and require explicit user approval.
- Execute only after successful verification, using the least-privileged account required.
- Avoid automatic privilege elevation. If administrative access is genuinely required, explain why and request it separately.
- Document secure manual installation and removal procedures so users can inspect and reverse the installation.
