T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:57- Finding
Unverified Remote Installer Scripts Are Downloaded and Executed Directly
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 57–61
Vulnerability Type: Remote payload retrieval and execution
Risk Level: Highbash 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 content retrieved from
cli.oomol.comdirectly into a command interpreter. The Unix command executes the HTTP response with Bash, while the Windows command executes it through PowerShell'sInvoke-Expression.Neither command pins a specific installer version nor verifies a cryptographic signature or checksum. Consequently, the effective code executed can change after the Skill has been reviewed. HTTPS protects data in transit under normal conditions but does not protect against a compromised hosting account, server, build pipeline, signing infrastructure, or legitimately published but maliciously altered installer.
Installation is only presented as a fallback when
oois unavailable, so this behavior is not part of routine connector operation. Nevertheless, following the documented fallback grants a remotely controlled script the full privileges of the invoking user. This exceeds the minimum privileges required merely to describe or invoke the connector.The audit did not independently confirm that connector requests exfiltrate unrelated sensitive information. Sending user-supplied connector input to OOMOL and Scrape Creators is disclosed and inherent to the declared remote scraping functionality. The file does not instruct the Agent to collect raw credentials, private keys, environment variables, or unrelated local files.
Attack Path
- The Agent attempts to invoke
oo, but the command is not installed. - Following the Skill's first-time setup instructions, the Agent or user runs one of the remote installation commands.
- The com ...[truncated 1342 chars]
- The Agent attempts to invoke
- Remediation
View remediation
Remediation Suggestions
- Remove direct
curl | bashandInvoke-Expressioninstallation patterns. - Direct users to a trusted, version-pinned package manager entry or a specific signed release artifact.
- Download the installer to a local file rather than executing the network response immediately.
- Publish an expected SHA-256 digest and verify it before execution. Prefer cryptographic signature verification using a trusted, separately distributed public key.
- Display or inspect the downloaded script and obtain explicit user approval before executing it.
- Pin both the installer and CLI version so the reviewed payload cannot change silently.
- Run installation with ordinary user privileges wherever possible and clearly warn users not to use an elevated shell unless a documented step strictly requires it.
- Apply equivalent verification controls to both the Bash and PowerShell installation paths.
- Keep installation outside autonomous Skill execution: if the CLI is absent, report the condition and provide verified manual setup instructions rather than automatically executing an installer.
- Remove direct
