T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:53- Finding
Unverified Remote Installation Scripts Executed Directly by Shells
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 53–61
Vulnerability Type: Remote payload retrieval and execution
Risk Level: HighVulnerable 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 first-time setup instructions download mutable scripts from
cli.oomol.comand immediately execute them with Bash or PowerShell. The instructions provide no version pinning, cryptographic signature verification, checksum validation, or opportunity to inspect the downloaded content before execution.HTTPS protects the connection in transit but does not make the remotely hosted scripts immutable or protect users if the hosting infrastructure, publishing account, domain, or upstream release process is compromised. Because the remote scripts are not included in the audited project, their effective behavior can change after this Skill has been reviewed.
Installing the
ooCLI may support the Skill's declared functionality, but piping an unverified remote response directly into a command interpreter is not the minimum-risk installation method.Attack Path
- The
oocommand is unavailable, causing the user or agent to consult the first-time setup instructions. - The user or agent executes one of the documented installation commands.
- An attacker compromises or gains control over the script-hosting endpoint, its publishing process, or associated infrastructure.
- The endpoint supplies an attacker-controlled shell or PowerShell payload.
- Bash or
Invoke-Expressionexecutes the response immediately without integrity verification. - The payload performs arbitrary actions with the permissions of the account that invoked the installer.
Impact Assessment
A malicious installer could execute arbitrary commands with the invoking user's privileges. Depending on those privileges and ...[truncated 477 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Remove the pipe-to-shell and
Invoke-Expressioninstallation commands. - Direct users to a pinned, official CLI release with an explicit version.
- Download the installation artifact to disk without executing it automatically.
- Publish and require verification of a cryptographic signature or trusted SHA-256 checksum before installation.
- Allow users to inspect the downloaded artifact or script before execution.
- Prefer a trusted platform package manager with version pinning and package-signature validation.
- If an installation script remains necessary, document its required permissions and instruct users not to run it with administrative privileges unless a specific installation step requires them.
- Keep the existing behavior of attempting normal connector operations before presenting setup instructions, thereby avoiding unnecessary installation execution.
- Remove the pipe-to-shell and
