T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:70- Finding
Unverified Remote Installer Download and Immediate Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 70–74
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 download scripts from an external server and immediately execute their contents through
bashor PowerShell'sInvoke-Expression. The retrieved payload is not pinned to a specific release, inspected before execution, or verified using a cryptographic checksum or publisher signature.Consequently, the effective code executed by this Skill can change after the reviewed
SKILL.mdfile has been published. Compromise of the hosting domain, DNS or TLS infrastructure, server account, release pipeline, or installer itself could convert these commands into an arbitrary-code execution mechanism.Installing the required CLI is relevant to the declared Sendlane connector functionality. However, immediate execution of an unverified, mutable remote response exceeds the minimum privileges and trust required for installation. The same weakness exists on both supported platform families.
Attack Path
- The
ooCLI is unavailable, causing the first-time setup instructions to apply. - An attacker compromises the remote installer, its hosting infrastructure, or the associated delivery pipeline.
- The response from
https://cli.oomol.com/install.shorhttps://cli.oomol.com/install.ps1is replaced with attacker-controlled code. - The installation command downloads the modified response.
- The pipe to
bashoriexexecutes the response immediately without integrity or authenticity verification. - The payload runs with the permissions of the user or agent process invoking the installation command.
Impact Assessm
...[truncated 638 chars]
- The
- Remediation
View remediation
Remediation Suggestions
- Do not pipe downloaded content directly into a shell or
Invoke-Expression. - Prefer an official operating-system package manager or a signed, versioned release artifact from a verifiable publisher.
- Pin the CLI to a specific reviewed version rather than retrieving a mutable installer.
- Download the installer to a local file without executing it.
- Verify a publisher signature and a pinned SHA-256 or stronger cryptographic digest before execution.
- Present the source, version, destination, expected file changes, and required permissions to the user.
- Obtain explicit user approval before executing any installer.
- Run installation with ordinary user privileges unless a documented step strictly requires elevation.
- Publish reproducible installer sources and document expected installed files so users can independently verify the package.
- Abort installation on redirects to unexpected domains, signature failures, checksum mismatches, or TLS errors.
- Do not pipe downloaded content directly into a shell or
