T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:75- Finding
Unverified Remote Installation Script Executed Through Bash
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 75
Vulnerability Type: Remote payload retrieval and immediate execution
Risk Level: Criticalbash curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / LinuxTechnical Analysis
The installation instruction downloads a mutable script from an external URL and pipes the response directly into Bash. The script is executed without version pinning, signature or checksum verification, local inspection, or confirmation of its final contents.
Although the URL uses HTTPS and belongs to the service named by the Skill, the executable payload is not included in the audited project and can change after review. Compromise of the remote host, publishing account, DNS/TLS path, or installation script could consequently turn this instruction into arbitrary code execution.
Installing software is not required for the Skill's core operation when the
ooCLI is already available. Directly executing an unverified installer also exceeds the minimum privileges needed to perform read-only RAWG queries.Attack Path
- The
ooCLI is absent, causing an action to fail withoo: command not found. - The Agent or user follows the documented first-time setup instruction.
curldownloads the current contents ofhttps://cli.oomol.com/install.sh.- The response is passed directly to Bash without verification or inspection.
- Any malicious or compromised content in that response executes with the privileges of the user running the command.
Impact Assessment
A compromised installer could execute arbitrary commands with the invoking user's privileges. This could expose files, credentials accessible to that user, shell configuration, and environment data; modify user-owned files; install additional software; or establish persistence where the current account has permission. The audited file does not prove that the current installer performs these ac ...[truncated 81 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Do not pipe a network response directly into a shell.
- Prefer an official, version-pinned package from a trusted package manager or a versioned release artifact.
- Publish and verify a cryptographic checksum or digital signature before execution.
- Download the installer to a local file, inspect it, and execute it only after explicit user approval.
- Pin the expected installer or CLI version so the effective code cannot change silently after the Skill is reviewed.
- Keep installation outside normal Skill execution and document it as a manual prerequisite.
- Run installation with standard-user privileges unless a specific, documented operation requires elevation.
