T03 · Remote Payload Retrieval and Execution
- Location
README.md:38- Finding
Unverified Remote Installation Script Executed Through a Shell Pipeline
- Content
View full analysis
Vulnerability Details
File Location:
README.md, lines 38–40
Vulnerability Type: Remote payload retrieval and execution
Risk Level: CriticalVulnerable Code
bash # 1. Install OpenClaw curl -fsSL https://openclaw.ai/install.sh | bashTechnical Analysis
The installation instructions retrieve a mutable script from an external URL and pass its response directly to Bash. The script is executed without prior inspection, version pinning, checksum verification, or cryptographic signature validation.
The reviewed package does not contain the remote script, so its effective behavior cannot be established by auditing this project. Its contents may also change after the Skill has been reviewed. Although installing OpenClaw is relevant to one documented usage method, immediate execution of an unverified remote response is not the minimum privilege or trust required. The project also documents a direct prompt-template usage method that does not require this installation command.
This creates a supply-chain execution channel. Compromise of the remote server, publishing process, DNS resolution, TLS trust chain, or hosting account could replace the expected installer with arbitrary shell commands.
Attack Path
- An attacker compromises the remote installation endpoint or another component trusted while resolving and retrieving the script.
- The attacker modifies the response from
https://openclaw.ai/install.shto include malicious shell commands. - A user follows the README and runs the documented pipeline.
curldownloads the attacker-controlled response.- The pipe sends that response directly to Bash without an opportunity for inspection or integrity verification.
- Bash executes the payload with all permissions available to the invoking user.
- The payload may access user-readable data, modify files, steal credentials available to the process, install additional software, or establi ...[truncated 695 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the
curl | bashpipeline from the documentation. - Prefer a trusted package manager with a pinned package version and documented publisher identity.
- If a standalone installer is necessary:
- Publish versioned, immutable artifacts.
- Provide a SHA-256 or stronger checksum through a separate trusted channel.
- Sign releases cryptographically and document signature verification.
- Instruct users to download the installer to a local file.
- Require users to verify the checksum or signature before execution.
- Allow inspection before running the script.
- Do not instruct users to run the installer with
sudoor elevated privileges unless a specific operation demonstrably requires it. - Document the files, network destinations, permissions, and system changes made by the installer.
- Retain and emphasize the direct prompt-template usage path, which does not require remote code execution.
- Pin documentation examples to a specific reviewed release rather than a mutable generic endpoint.
A safer high-level workflow is:
bash curl -fL -o openclaw-install.sh "https://example.invalid/releases/vX.Y.Z/install.sh" echo "<published-sha256> openclaw-install.sh" | sha256sum --check - less openclaw-install.sh bash openclaw-install.shThe placeholder URL and checksum must be replaced with an authentic, immutable release and independently published integrity value.
- Remove the