T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:70- Finding
Unverified Remote Shell Script Execution on macOS and Linux
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 70
Vulnerability Type: Remote payload retrieval and execution
Risk Level: HighVulnerable Code:
bash curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / LinuxTechnical Analysis
The installation instruction downloads a mutable shell script from an external URL and pipes it directly into
bash. The downloaded content is neither pinned to a specific version nor authenticated through a published checksum or cryptographic signature. It is also not saved for inspection before execution.Installing the
ooCLI supports the Skill's declared EchoTik functionality, but immediate execution of arbitrary remote content is not the minimum privilege or safest mechanism necessary to perform that installation. The effective code can change after the Skill has been reviewed. Compromise of the remote hosting environment, domain, DNS resolution, TLS termination infrastructure, or release process could therefore turn this instruction into an arbitrary-code execution channel.Attack Path
- The
oocommand is unavailable, causing the documented first-time setup condition to occur. - An agent or user follows the installation instruction in
SKILL.md. - An attacker compromises or maliciously changes the script served from
https://cli.oomol.com/install.sh, or compromises infrastructure involved in delivering it. curldownloads the attacker-controlled content without version or integrity validation.- The shell executes the content immediately as the account that invoked the command.
- The payload can access resources available to that account and may download or install additional components.
Impact Assessment
Successful exploitation provides arbitrary command execution with the privileges of the invoking user. The payload could read or modify user-accessible files, access credentials or session material available to that ...[truncated 452 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Replace the pipe-to-shell instruction with a version-pinned package or release artifact from a documented distribution channel.
- Download the installer to a local file rather than executing the network response immediately.
- Publish a SHA-256 checksum and, preferably, a cryptographic signature through an independently secured channel.
- Verify the checksum and signature before execution and abort installation if verification fails.
- Display or permit inspection of the downloaded script before it is run.
- Execute the installer without elevated privileges unless a narrowly defined installation step genuinely requires them.
- Document the files, directories, and network destinations used by the installer.
- Prefer a platform package manager with signed repository metadata and reproducible, versioned releases.
