T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:60- Finding
Unverified Remote Installer Download and Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 60–64
Vulnerability Type: Remote payload retrieval and immediate 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 installation instructions pipe remotely retrieved content directly into a command interpreter. The Bash command sends the current response from
cli.oomol.comdirectly tobash, while the PowerShell command passes it toInvoke-Expression. Neither instruction pins an installer version, verifies a cryptographic signature or checksum, nor gives the user an opportunity to inspect the downloaded script before execution.Consequently, the effective code executed by these commands can change after the Skill has been reviewed. Compromise of the hosting infrastructure, domain, DNS path, deployment pipeline, or installer itself could turn these instructions into an arbitrary-code-execution channel.
Installing the CLI is only a fallback when
oois unavailable, and the declared runtime permission is limited toBash(oo *). Automatic execution of mutable remote scripts therefore exceeds the minimum privileges required to use an already-installed Recruiterflow connector.Attack Path
- The
oocommand is unavailable, causing the user or agent to consult the first-time setup instructions. - An attacker compromises or gains influence over the installer response, its hosting pipeline, or the network resolution path.
- The victim runs the documented
curl | bashorirm | iexcommand. - The shell immediately interprets the attacker-controlled response without integrity or authenticity verification.
- The payload executes with all privileges available to the invoking user and can perform further malicious actions.
Impact Assessment
...[truncated 820 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Remove direct
curl | bashandirm | iexinstallation instructions. - Prefer a trusted platform package manager and pin the CLI to a reviewed version.
- If script-based installation is unavoidable, download a versioned artifact to disk rather than executing the HTTP response directly.
- Publish a SHA-256 checksum and, preferably, a cryptographic signature through an independently secured channel.
- Verify the checksum and signature before execution, fail closed on any mismatch, and permit inspection of the downloaded script.
- Document that installation must run without administrator or root privileges unless a specific, justified operation requires elevation.
- Pin redirects and enforce HTTPS certificate validation; avoid mutable, unversioned installer endpoints.
- Apply equivalent verification controls to both the Bash and PowerShell installation paths.
- Remove direct
