T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:59- Finding
Unverified Remote Installation Scripts Are Downloaded and Executed Directly
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 59–63
Vulnerability Type: Unverified 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 installation instructions download scripts from
cli.oomol.comand immediately execute them through Bash or PowerShell. The Skill does not pin a script version, verify a cryptographic checksum or digital signature, save the script for inspection, or otherwise ensure that the executed content is identical to the content reviewed during this audit.Because the payload is remotely hosted and mutable, its effective behavior can change after the Skill package has been reviewed. HTTPS protects the connection in transit but does not protect against compromise of the distribution server, domain, hosting account, deployment pipeline, or signing infrastructure. If any of those components are compromised, arbitrary commands supplied by an attacker would be executed with the privileges of the user running the installation command.
Installing the external CLI may be relevant to first-time setup, but immediate execution of an unverified remote script is not the least-privileged or least-risk method necessary to support VATlayer operations.
Attack Path
- The Agent attempts to use the
ooCLI and receives anoo: command not founderror. - Following the Skill instructions, it invokes the applicable installation command.
- The command retrieves a mutable script from
https://cli.oomol.com/install.shorhttps://cli.oomol.com/install.ps1. - Bash or PowerShell executes the downloaded response without prior inspection or integrity verification.
- If the remote endpoint or its delivery chain has been compromised, attacker-controlled commands execute under the invoking user’s accoun ...[truncated 863 chars]
- The Agent attempts to use the
- Remediation
View remediation
Remediation Suggestions
- Remove both direct download-and-execute pipelines.
- Direct users to version-pinned release artifacts from the official CLI repository or a trusted package manager.
- Publish and verify a SHA-256 or stronger checksum for each platform-specific artifact. Prefer a digitally signed release whose signature is verified against a documented, trusted public key.
- Download the installer to a local file rather than piping it directly into an interpreter.
- Require the user to review and explicitly approve the installation before execution.
- Run installation with ordinary user privileges unless a specific operation demonstrably requires elevation.
- Pin the expected CLI version so that future upstream changes do not silently alter the reviewed behavior.
- For automated environments, use an internally mirrored and integrity-verified artifact rather than executing content from a mutable URL.
A safer general workflow is:
bash # Download a version-pinned artifact without executing it. curl -fL -o oo-installer.sh "https://trusted.example/path/to/pinned/version/install.sh" # Verify against a checksum obtained through a trusted channel. echo "<EXPECTED_SHA256> oo-installer.sh" | sha256sum --check - # Inspect and execute only after explicit user approval. less oo-installer.sh bash oo-installer.sh
