T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:55- Finding
Unverified Remote Installer Scripts Executed Directly by Shells
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 55-59
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 pass content retrieved from a remote server directly to
bashor PowerShell'sInvoke-Expressionalias,iex. The downloaded scripts are neither pinned to a reviewed version nor verified with a cryptographic signature or expected checksum before execution.Consequently, the effective code can change after the Skill has been audited. Compromise of the hosting service, publishing account, domain, DNS resolution, or relevant TLS trust infrastructure could cause attacker-controlled commands to execute. Even without infrastructure compromise, an upstream script update would execute without local review.
Installing the CLI is only a conditional setup operation and is not necessary to the core task of validating an email address when the CLI is already installed. Automatically executing a mutable remote installer therefore exceeds the minimum privileges needed for the declared Mailboxlayer functionality.
Attack Path
- The
ooCLI is unavailable, causing the documented first-time setup fallback to be used. - The user or agent runs the applicable installation command.
curlorirmretrieves a mutable script fromcli.oomol.com.- An attacker who controls or has compromised the delivered response inserts arbitrary shell commands.
- The pipe to
bashor invocation throughiexexecutes those commands immediately under the invoking user's account. - The payload can access resources available to that account and may retrieve additional payloads, modify files, or establish persistence.
Impact Assessment
Successful exploi ...[truncated 626 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Remove all direct
curl | bashandirm | iexinstallation instructions. - Distribute the CLI through a reputable platform package manager or a pinned release artifact.
- Pin installation instructions to a specific, reviewed CLI version rather than a mutable generic installer URL.
- Publish cryptographic checksums and signed release manifests through a separately protected channel.
- Download the artifact to a local file, verify its signature and checksum, and only then execute or install it.
- Display the verified artifact and intended installation effects to the user and obtain explicit approval before execution.
- Run installation with ordinary user privileges unless a narrowly defined operation demonstrably requires elevation.
- Keep software installation outside automated Skill execution; when the CLI is missing, return safe manual setup guidance instead of autonomously installing it.
- Remove all direct
