T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:21- Finding
Remote installation script is downloaded and executed without verification
- Content
View full analysis
**Pre-check: Aliyun CLI >= 3.3.3 required** > > Run `aliyun version` to verify >= 3.3.3. If not installed or version too low, > run `curl -fsSL https://aliyuncli.alicdn.com/setup.sh | bash` to update, > or see [`references/cli-installation-guide.md`](references/cli-installation-guide.md) for installation instructions. ``` ### Technical Analysis The command pipes an HTTPS response directly into Bash. Consequently, the code reviewed in this project is not the code that will necessarily execute when the Skill is used. The effective payload remains mutable and is controlled by the remote distribution endpoint. No fixed version, cryptographic checksum, signature, or local review step is required before execution. HTTPS authenticates the connection to the endpoint but does not protect against compromise of the hosting infrastructure, distribution account, DNS/TLS trust chain, or future unauthorized modification of the hosted script. Direct remote shell execution is not necessary for the declared PAI DSW management functionality. The documentation already offers package-manager and binary installation alternatives, so this behavior exceeds the minimum safe installation mechanism. ### Attack Path 1. The Aliyun CLI is absent or does not meet the required version. 2. The Agent follows the Skill's update instruction. 3. `curl` retrieves the current contents of `setup.sh` from the remote endpoint. 4. The response is passed directly to Bash without being saved or inspected. 5. Any commands in the response execute with the privileges and environment of the user running the Agent. 6. A malicious payload could modify user files, read accessible credentials, install altered tooling, or attempt to obtain additional privileges. ### Impact Assessment A malicious remote response ...[truncated 555 chars]- Remediation
View remediation
