T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:57- Finding
Unverified Remote Shell Script Execution on macOS and Linux
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 57
Vulnerability Type: Remote payload retrieval and execution
Risk Level: Criticalbash curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / LinuxTechnical Analysis
The installation instruction pipes a mutable remote response directly into
bash. The downloaded content is neither version-pinned nor validated using a cryptographic checksum or digital signature. It is also not saved for inspection before execution.Although installing the
ooCLI supports the Skill's declared functionality, direct execution of unverified network content is not the least-risk installation method. The effective code can change after the Skill has been reviewed. Compromise of the vendor's hosting infrastructure, DNS, TLS termination, publishing account, or build pipeline could turn this command into an arbitrary-code-execution mechanism.Attack Path
- The user or agent attempts to use the Skill on a system where
oois unavailable. - The
oo: command not foundfallback directs it to run the documented pipeline. curlretrieves the current response fromhttps://cli.oomol.com/install.sh.- The response is passed directly to
bashwithout inspection or integrity verification. - A compromised or malicious response executes with the privileges of the invoking user.
- The payload could access local data, modify files, steal credentials available to that account, or establish persistence.
Impact Assessment
Successful exploitation provides arbitrary command execution under the invoking user's account. The accessible scope includes files, credentials, environment data, network resources, and processes available to that user. If the command is run by a privileged account or through privilege elevation, the impact could extend to system-wide compromise.
- The user or agent attempts to use the Skill on a system where
- Remediation
View remediation
Remediation Suggestions
- Remove the
curl | bashinstallation pattern. - Prefer a reviewed package distributed through a trusted platform package manager.
- Pin the installer or package to an explicit version.
- If a standalone script is required, download it to a local file first.
- Verify a vendor signature and a separately distributed, version-specific cryptographic checksum before execution.
- Allow the user to inspect the downloaded script.
- Require explicit user approval before installing software; an agent should not install it automatically after an action failure.
- Execute the installer with the minimum required privileges and avoid unnecessary use of
sudoor privileged accounts.
- Remove the
