T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:503- Finding
Unverified Remote Installation Script Executed Directly by Bash
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:503
Vulnerability Type: Remote payload retrieval and immediate execution
Risk Level: CriticalVulnerable Code:
bash curl -fsSL https://molt.bot/install.sh | bashTechnical Analysis
The installation command downloads a mutable script from an external domain and passes it directly to Bash. The script is not pinned to a reviewed version, downloaded for inspection, authenticated through a code-signing mechanism, or checked against a trusted cryptographic digest.
HTTPS protects the transport connection but does not establish that the server, its current script, or future versions of the script are trustworthy. The effective payload can change after this Skill has been reviewed. The use of
-salso suppresses normal progress output, reducing visibility during execution.This behavior is particularly dangerous because the same guide recommends unrestricted passwordless sudo and alternatively suggests operating as root. Under either configuration, commands delivered by the remote server could obtain full control of the WSL environment.
Attack Path
- A user follows the installation guide.
- The
molt.botserver, DNS resolution, hosting account, or deployment pipeline is compromised, or the hosted script is intentionally changed. curlretrieves the modified script.- The pipe sends the response directly to Bash without an inspection or integrity-verification step.
- The script executes with the current user's permissions.
- If the user is root or has the recommended
NOPASSWD: ALLrule, the payload invokessudoand gains root privileges without additional user approval. - The payload can modify the WSL filesystem, steal locally available credentials, install services, or alter OpenClaw configuration.
Impact Assessment
Successful exploitation provides arbitrary command execution in WSL. The immediate scope is the current L ...[truncated 329 chars]
- Remediation
View remediation
Remediation Suggestions
- Do not pipe network responses directly into a shell.
- Use an official, versioned OpenClaw release from a verified project repository.
- Pin the installer to an immutable release tag or commit.
- Publish a trusted SHA-256 digest or cryptographic signature through an independent authenticated channel.
- Download the installer to a local file, verify its digest or signature, and allow it to be reviewed before execution.
- Run installation as an unprivileged account and request elevation only for narrowly defined operations.
- Document the files, packages, network connections, and services that the installer creates.
- Fail closed when integrity verification cannot be completed.
