T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:31- Finding
Mutable Remote Installation Script Is Executed Directly Through a Shell
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, lines 31-34
Vulnerability Type: Remote payload retrieval and immediate execution
Risk Level: CriticalVulnerable Code:
markdown **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` for installation instructions.Technical Analysis
The Skill instructs the Agent to download a mutable shell script from an external URL and pipe it directly into
bash. The downloaded content is executed before the user or Agent can inspect it. No fixed version, expected SHA-256 checksum, cryptographic signature, or authenticated release manifest is specified.The domain appears related to Alibaba Cloud, but domain reputation alone does not establish the integrity of content that may change after this Skill has been reviewed. Compromise of the hosting infrastructure, CDN, publishing account, DNS/TLS trust chain, or installation script could therefore transform an apparently legitimate prerequisite step into arbitrary local code execution.
Installing or updating Aliyun CLI may be necessary for the declared cost-analysis functionality, but immediate pipe-to-shell execution is not the minimum-risk installation mechanism. The project already provides manual package and binary installation alternatives, making this unsafe execution method unnecessary.
Attack Path
- A user invokes the Skill for MaxCompute cost analysis.
- The Agent determines that Aliyun CLI is absent or older than the required version.
- Following the Skill instructions, the Agent requests
https://aliyuncli.alicdn.com/setup.sh. - The response body is passed directly to
bashwithout inspection or integrity verification. - If the remote response has been maliciously altered, arbitrary shell comman ...[truncated 1258 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the
curl ... | bashinstruction entirely. - Prefer an operating-system package manager with a trusted repository, such as a pinned Homebrew package version where supported.
- If direct binary installation is required:
- Download a versioned artifact rather than a mutable
latestURL. - Download the checksum and signature separately.
- Validate the publisher's cryptographic signature.
- Compare the artifact against a documented SHA-256 checksum.
- Abort installation if verification fails.
- Download a versioned artifact rather than a mutable
- Separate download and execution into distinct, user-visible steps so the artifact can be inspected before use.
- Require explicit user consent before installing or replacing host-level software.
- Perform installation using the least-privileged account possible and elevate only for the narrowly required file operation.
- Document the exact supported CLI version and trusted release source to make the installed payload reproducible and auditable.
- Remove the
