T03 · Remote Payload Retrieval and Execution
- Location
references/Quick-Start_EN.md:7- Finding
Execution of a Mutable Remote Installer
- Content
View full analysis
# Example: ./scripts/install.sh Mingde LaoZhao ``` ### Technical Analysis The setup guide instructs users to clone a mutable external repository and execute its `scripts/install.sh` file. That installer is not included in the audited package, so its implementation and security properties cannot be verified from this artifact. Because the command does not pin the repository to an audited commit or verify a cryptographic digest or signature, the effective payload can change after this Skill has been reviewed. Compromise of the external account, repository, default branch, or distribution channel would allow an attacker to replace the installer with arbitrary shell commands. The documentation states that the installer creates core files and adds A2A public-registry configuration, indicating that it is expected to modify the agent environment rather than merely display information. ### Attack Path 1. A user or agent follows the bundled quick-start guide. 2. The current default branch of the external repository is cloned. 3. No commit pin, signature, or checksum is validated. 4. The user executes `scripts/install.sh`. 5. Any commands currently present in that remote script run with the invoking user's privileges. 6. A compromised installer could read or modify agent configuration, memory, workspace files, credentials accessible to that user, or network settings. ### Impact Assessment Successful exploitation provides arbitrary command execution under the account running the installer. The accessible scope may include: - OpenClaw workspace and agent configuration files. - Persistent memory and identity files. ...[truncated 462 chars]- Remediation
View remediation
``` 3. Publish and verify a cryptographic hash or signed release before execution. 4. Display the installer contents and an exact list of affected files before requesting explicit user approval. 5. Run installation with minimum privileges in a restricted workspace. 6. Do not automatically configure external services as part of an unrelated local installation. 7. Document rollback steps and provide a dry-run mode that makes no changes. ]]>
