T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:73- Finding
Unverified Remote Installer Downloaded and Executed Directly
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 73–77
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 retrieve mutable scripts from
cli.oomol.comand immediately pass their contents to a command interpreter. The downloaded scripts are not included in the audited project, and the instructions provide no version pinning, cryptographic signature verification, checksum validation, or opportunity to inspect the files before execution.Consequently, the code ultimately executed can change after this Skill has been reviewed. Compromise of the distribution server, its publishing process, or the delivered installer could cause arbitrary commands to run in the Agent or user's security context.
Installing the required CLI may be legitimate, but executing an unverified remote script directly is not the minimum privilege or safest mechanism necessary to provide that functionality.
Attack Path
- The
ooexecutable is unavailable, causing the Agent or user to follow the first-time setup instructions. - The Agent executes the documented
curl | bashorirm | iexcommand. - The command retrieves the current installer from the external server without verifying a pinned version, signature, or checksum.
- The shell immediately interprets the response as executable code.
- If the remote installer or its distribution path has been compromised, attacker-controlled commands execute with the invoking account's privileges.
Impact Assessment
A malicious installer could perform any operation available to the invoking account, including:
- Reading or modifying user-accessible files.
- Accessing credentials, environme ...[truncated 750 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Remove the direct
curl | bashandirm | iexinstallation commands. - Prefer an authenticated operating-system package repository or another package manager that supports signed, versioned releases.
- If script-based installation remains necessary:
- Download a specific, immutable installer version to a local file.
- Publish and verify a cryptographic signature using a trusted public key.
- At minimum, verify a pinned cryptographic checksum obtained through an independently authenticated channel.
- Inspect the downloaded file before execution.
- Require explicit user approval before running it.
- Never recommend executing the installer with administrator or root privileges unless individual operations have been documented as requiring those privileges.
- Pin the CLI version used by the Skill and document a controlled update process so that installation behavior cannot change silently after review.
- Keep installation separate from normal Grafana actions; failure due to a missing CLI should produce instructions rather than automatically executing remote installation code.
- Remove the direct
