T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:59- Finding
Unverified Remote Installation Scripts Executed Directly by Shell
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 59–63
Vulnerability Type: Remote payload retrieval and execution
Risk Level: Criticalbash curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linuxpowershell irm https://cli.oomol.com/install.ps1 | iex # Windows PowerShellTechnical Analysis
The installation instructions download mutable scripts from an external server and pass the responses directly to Bash or PowerShell. Neither command allows the user to inspect the downloaded content before execution, and no version pinning, cryptographic signature verification, or checksum validation is performed.
Consequently, the code that executes can differ from the content available when the Skill was audited. Compromise of the hosting service, publishing account, DNS resolution, or TLS trust chain could turn these installation commands into an arbitrary-code-execution channel. Although installing the
ooCLI supports the declared connector functionality, executing an unverified network response directly in a shell exceeds the minimum mechanism necessary to perform that installation.Attack Path
- The
ooCLI is unavailable, causing the user or agent to follow the first-time setup instructions. - An attacker compromises or otherwise gains control over the remote installation response or its delivery path.
- The attacker modifies
install.shorinstall.ps1to include malicious commands. - The setup command retrieves the modified response and immediately pipes it to Bash or
Invoke-Expression. - The malicious commands execute with the privileges of the user running the installation command, without a review or integrity-verification step.
Impact Assessment
Successful exploitation permits arbitrary command execution under the invoking user's account. The resulting access could allow an attacker to read or modify files available to that account, ...[truncated 760 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Remove the direct
curl | bashandirm | iexinstallation patterns. - Prefer an official operating-system package manager with signed repository metadata and a version-pinned package.
- If a standalone artifact is required, download it to a local file without executing it automatically.
- Pin the download to a specific release version rather than a mutable generic installation URL.
- Publish and verify a cryptographic signature from a separately trusted signing key. At minimum, verify a release-specific SHA-256 digest obtained through an independent trusted channel.
- Allow the user to inspect the downloaded installer before execution.
- Require explicit user approval before installing software, and clearly state which files, directories, and system settings the installer will modify.
- Run installation with ordinary user privileges whenever possible; request elevated privileges only for a narrowly defined operation that genuinely requires them.
- Document a manual installation procedure and provide rollback or uninstall instructions.
- Remove the direct
