T03 · Remote Payload Retrieval and Execution
- Location
README.md:10- Finding
Mutable Remote Installer Is Executed Directly by a Shell
- Content
View full analysis
Vulnerability Details
File Location:
README.md, line 10
Vulnerability Type: Remote payload retrieval and execution
Risk Level: CriticalVulnerable Code:
bash curl -sL https://api.lobstermail.ai/install | shTechnical Analysis
The installation command downloads content from a mutable remote endpoint and passes it directly to
sh. The response is executed without displaying it for review, pinning it to an audited version, validating a checksum, or verifying a cryptographic signature.The installer returned by
/installis not included in the audited project, so its behavior and required privileges cannot be statically verified. Although installing the Skill is related to the declared functionality, arbitrary shell execution is broader than the minimum privilege required to copy a Skill definition into the OpenClaw skills directory.HTTPS protects transport under ordinary conditions, but it does not protect against compromise of the service, deployment pipeline, CDN, DNS infrastructure, TLS credentials, or maintainer account. Because the endpoint is mutable, the effective installer can also change after this project has been reviewed.
Attack Path
- An attacker compromises the LobsterMail installer endpoint or an associated deployment or distribution component.
- The attacker changes the endpoint response to include malicious shell commands.
- A user follows the documented installation command.
curlretrieves the modified response and immediately streams it intosh.- The malicious commands execute with all permissions available to the invoking user, without a separate review or confirmation step.
Impact Assessment
Successful exploitation provides arbitrary command execution under the invoking user's account. The payload could read or modify user-accessible files, steal credentials and API tokens, alter OpenClaw configuration, install persistence, replace other Skill ...[truncated 341 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the
curl | shinstallation pattern. - Publish a versioned installer or Skill artifact through a controlled release process.
- Require users to download the artifact as a separate step before execution.
- Publish and require verification of a SHA-256 digest and, preferably, a signature tied to a documented release key.
- Pin installation instructions to an immutable version rather than a mutable endpoint.
- Include the installer source in the repository so its behavior can be reviewed.
- Ensure the installer operates without elevated privileges and only writes to the required Skill directory.
- Use strict shell settings and explicit validation if a shell installer remains necessary.
- Remove the
