T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:42- Finding
Mutable Remote Installation Script Executed Directly by Bash
- 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 install/update, > or see [references/cli-installation-guide.md](references/cli-installation-guide.md) for installation instructions. > Then **[MUST]** run `aliyun configure set --auto-plugin-install true` to enable automatic plugin installation. > Then **[MUST]** run `aliyun plugin update` to ensure that any existing plugins on your local machine are always up-to-date. ``` ### Technical Analysis The installation command downloads a mutable remote shell script and immediately sends it to Bash. There is no opportunity to inspect the retrieved content, and the workflow performs no version pinning, signature validation, or checksum verification. HTTPS protects the connection in transit but does not establish that the current remote payload is identical to the version reviewed with this Skill. Compromise of the publishing account, origin server, CDN, or associated delivery infrastructure could therefore change the effective code executed by the Skill after review. Installing the Aliyun CLI supports the declared functionality, but direct remote-to-shell execution is not the minimum-risk method required to install it. ### Attack Path 1. The Skill determines that Aliyun CLI is absent or older than version 3.3.3. 2. The Skill executes the documented `curl` pipeline. 3. An upstream compromise causes `setup.sh` to contain attacker-controlled commands. 4. Bash executes those commands immediately without local verification. 5. The payload operates with the privileges and environment of the user running the Skill. ### Impact Assessment A succe ...[truncated 431 chars]- Remediation
View remediation
