T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:59- Finding
Unverified Remote Installation Scripts Are Executed Directly
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:59-63
Vulnerability Type: Remote payload retrieval and execution
Risk Level: HighComplete Code Snippet:
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 retrieve mutable scripts from
cli.oomol.comand pass their contents directly to a command interpreter. The scripts are executed without version pinning, cryptographic signature verification, checksum validation, or an intermediate inspection step.Consequently, the code ultimately executed can differ from the content available when this Skill was audited. Compromise of the remote hosting infrastructure, release pipeline, domain, or applicable network trust chain could turn these installation commands into an arbitrary-code execution channel.
Installing the CLI is not required for ordinary Skill operation when it is already present. Although the instructions limit this fallback to cases where
oois unavailable, installation still exceeds the minimum privileges needed to perform Eventee read operations and introduces avoidable supply-chain risk. No evidence in the reviewed file establishes that either remote script is itself malicious; the vulnerability is the unverified download-and-execute mechanism.Attack Path
- The
ooexecutable is absent or cannot be resolved through the current environment. - The resulting
oo: command not foundcondition causes the Agent or user to follow the first-time setup instructions. - The shell retrieves the current script from
https://cli.oomol.com/install.shorhttps://cli.oomol.com/install.ps1. - An attacker who has compromised the remote script, hosting pipeline, domain, or relevant trust chain supplies modified executable content.
bashor PowerShell immediatel ...[truncated 850 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Remove direct
curl | bashandirm | iexinstallation patterns. - Prefer a trusted platform package manager or a version-pinned release artifact from a verified publisher.
- Download the installer to a local file rather than piping it directly to an interpreter.
- Verify a publisher-provided cryptographic signature or a checksum obtained through an independently protected channel.
- Display the installer source, version, destination, and expected system changes before execution.
- Require explicit user approval before downloading or running installation code.
- Execute the installer with the least-privileged account available and avoid elevation unless a documented operation strictly requires it.
- Pin an approved CLI version and document a controlled update process so reviewed installer behavior cannot change silently.
- Remove direct
