T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:64- Finding
Unverified Remote Shell Script Execution on macOS and Linux
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 64
Vulnerability Type: Remote payload retrieval and execution
Risk Level: Criticalbash curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / LinuxTechnical Analysis
The installation instruction pipes a mutable response from an external URL directly into Bash. The remote script is executed without a pinned version, cryptographic checksum, digital-signature verification, local inspection, or separate user confirmation.
HTTPS protects the connection in transit but does not establish that the downloaded script is safe. Compromise of the hosting service, publisher account, DNS or certificate infrastructure, or deployment pipeline could cause arbitrary attacker-controlled shell commands to be returned. The effective payload can also change after the Skill has been reviewed.
Installing the required CLI may support the declared functionality, but direct remote-to-shell execution is not necessary. It gives the remote endpoint code-execution privileges beyond those required for the Skill's read-only Chuhaijiang operations.
Attack Path
- An
oocommand fails because the CLI is unavailable. - The agent follows the documented first-time setup procedure.
curlretrieves the current response fromhttps://cli.oomol.com/install.sh.- The response is passed directly to Bash without verification or inspection.
- If the remote source or delivery chain has been compromised, attacker-controlled commands execute with the permissions of the user running the agent.
Impact Assessment
A malicious installer could read or modify any files accessible to the current user, steal environment variables or locally available credentials, download additional payloads, alter command-line tools, or establish persistence. If the agent or shell is running with elevated privileges, the payload could affect the broader operating system. The repository ...[truncated 155 chars]
- An
- Remediation
View remediation
Remediation Suggestions
- Do not pipe network responses directly into a shell.
- Distribute a version-pinned CLI package or installer artifact through a trusted package manager with publisher-signature verification.
- If a standalone installer is required, download it to a local file first and verify a publisher-provided cryptographic signature or a checksum obtained through an independently trusted channel.
- Pin the expected CLI version, artifact URL, signer identity, and digest in the setup documentation.
- Allow the user to inspect the downloaded file and require explicit approval before executing it.
- Run installation with ordinary user privileges unless a documented operation strictly requires elevation.
- Prefer instructions similar to: download artifact, verify signature or SHA-256 digest, inspect, and then execute the verified local file.
