T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:59- Finding
Unverified Remote Installer Downloaded and Executed Directly
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 59–63
Vulnerability Type: Remote payload retrieval and execution
Risk Level: CriticalVulnerable 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 installation instructions retrieve mutable content from external URLs and pass the responses directly to command interpreters. Neither command saves the installer for inspection nor verifies its version, checksum, or cryptographic signature before execution.
Consequently, the effective code executed by this Skill can change after the package has been reviewed. An attacker who compromises the installer host, its publishing pipeline, the associated deployment credentials, or a relevant network trust dependency could replace the response with arbitrary commands.
Installing the required CLI is related to the declared SearchApi functionality. However, immediate execution of an unpinned and unverified network response is not the minimum privilege or safest mechanism needed to install it. The Windows instruction has the same underlying weakness as the Unix instruction:
Invoke-RestMethodretrieves the response andInvoke-Expressionimmediately evaluates it as PowerShell code.Attack Path
- The
ooCLI is absent, and a user or agent follows the documented first-time setup procedure. - An attacker compromises or gains control over the remote installer response, such as through the hosting infrastructure or release pipeline.
- The victim executes the documented
curl | bashorirm | iexcommand. - The shell evaluates the attacker-controlled response without prior inspection or integrity verification.
- The payload performs arbitrary actions with the permissions of the invoking user.
Impact Assessment
Successful exploitation pro ...[truncated 767 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Remove direct
curl | bashandirm | iexinstallation pipelines. - Prefer a trusted operating-system package manager or an official, version-pinned release package.
- Download the installer or binary without executing it automatically.
- Pin an immutable release version rather than using mutable
install.shorinstall.ps1endpoints. - Publish and verify a SHA-256 or stronger digest obtained through an independently protected channel.
- Verify a cryptographic release signature against a pinned, documented signing key.
- Allow the user to inspect the downloaded artifact and display the filesystem, network, and privilege changes it will make.
- Require explicit user approval before executing installation code.
- Run installation with ordinary user privileges unless a specific operation demonstrably requires elevation.
- If an automated installer remains necessary, fail closed when version, checksum, signature, or publisher verification fails.
- Remove direct
