T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:57- Finding
Unverified Remote Installer 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: Criticalbash 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 pipe remotely retrieved content directly into Bash or PowerShell. Neither command pins the installer to an immutable version, verifies a cryptographic signature or checksum, nor gives the user an opportunity to inspect the downloaded script before execution.
Consequently, the effective executable payload can change after the Skill has been audited. Compromise of the remote domain, DNS or network path, hosting infrastructure, TLS termination, or installer publishing account could turn these installation commands into arbitrary code-execution mechanisms. The Unix command also uses quiet curl options, limiting visibility into the transfer.
Installing a connector CLI can be necessary for the declared functionality, but immediate execution of an unverified remote response is not the minimum privilege or safest installation method required to query the read-only 1Password Events API.
Attack Path
- The intended
oocommand is unavailable, causing the user or Agent to consult the first-time setup instructions. - An attacker compromises the installer publishing pipeline, hosting infrastructure, domain resolution, or another trusted delivery component.
- The attacker replaces the expected installer response with a malicious shell or PowerShell payload.
- The documented command retrieves the mutable response from
cli.oomol.com. - The pipe passes the response directly to Bash or
Invoke-Expressionwithout integrity verification or inspection. - The malicious payload executes with all permissions available to the invoking user.
...[truncated 664 chars]
- The intended
- Remediation
View remediation
Remediation Suggestions
- Remove both direct
curl | bashandirm | iexinstallation patterns. - Use a trusted operating-system package manager or publish versioned release artifacts at immutable URLs.
- Pin the CLI to a reviewed version rather than retrieving an always-current installer.
- Download the artifact to a local file without executing it automatically.
- Publish a cryptographic signature or SHA-256 digest through an independently protected channel and require verification before execution.
- Permit inspection of the installer and require explicit user approval before running it.
- Run installation with ordinary user permissions unless a documented operation strictly requires elevation.
- Do not let the Agent automatically install tooling merely because an API action failed; distinguish command-not-found errors from authentication, connection, and service errors.
- Document that 1Password event requests and responses are processed by OOMOL so users can evaluate the sensitivity and trust implications of using the intermediary.
- Remove both direct
