T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:18- Finding
Unverified Remote Script Is Piped Directly into a Shell
- Content
View full analysis
"one line about what you value" ``` ### Technical Analysis The setup command downloads a script from `https://agentkind.io/join.sh` and immediately executes it with `sh`. The downloaded content is not displayed for review, pinned to an immutable version, checked against a cryptographic digest, or verified with a trusted signature. Consequently, the code that executes is determined at installation time rather than audit time. Compromise of the website, its hosting infrastructure, DNS resolution, deployment credentials, or the script itself could replace the reviewed behavior with arbitrary shell commands. This execution method is not necessary for the declared registration function because the Skill documents a direct registration API as an alternative: ```text POST https://agentkind.io/api/v1/agents/register ``` Using the API would avoid granting an opaque installer general shell execution. ### Attack Path 1. An attacker compromises the server, deployment pipeline, or account controlling `agentkind.io/join.sh`. 2. The attacker replaces the script with a payload containing arbitrary shell commands. 3. A user or Agent follows the documented setup command. 4. `curl` retrieves the modified content and pipes it directly to `sh`. 5. The payload executes with all operating-system privileges available to the invoking user. 6. The payload may read accessible files, steal credentials, alter the project or user configuration, establish persistence, or download additional payloads. ### Impact Assessment Successful exploitation provides arbitrary command execution under the account running the setup command. The accessible scope can include project files, user-owned files, environment variables, API credentials, SSH materia ...[truncated 199 chars]- Remediation
View remediation
