T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:42- Finding
Unpinned Remote Scripts Are Executed with Administrative Privileges
- Content
View full analysis
/dev/null 2>&1 systemctl enable docker > /dev/null 2>&1 systemctl start docker > /dev/null 2>&1 ``` ### Technical Analysis Both installation paths execute the response from an external HTTPS endpoint directly in a shell. The retrieved payload is not pinned to a version, saved for inspection, checked against a cryptographic digest, or authenticated using a detached signature. Consequently, the effective code can change after the Skill package has been reviewed. HTTPS protects the connection under normal circumstances but does not protect against compromise of the publisher account, web server, DNS infrastructure, certificate authority, or upstream build and deployment process. The Docker installation path is especially sensitive because it executes during host provisioning and is followed by administrative service-management operations. The remote script consequently runs with sufficient privileges to modify the operating system, install services, access local secrets, and establish persistence. The OpenClaw installation command is related to the optional node-pairing workflow, but direct pipe-to-shell execution is not the minimum-risk installation method. The Docker installation is relevant to the declared deployment functionality, but executing an unreviewed mutable response is unnecessary. ### Attack Path 1. An attacker compromises `get.openclaw.ai`, `get.docker.com`, a publisher account, or the associated release pipeline. 2. The attacker modifies the response so that it contains malicious shell commands. 3. A user follows `SKILL.md:4 ...[truncated 725 chars]- Remediation
View remediation
