T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:53- Finding
Unverified Remote Installer Downloaded and Executed Through a Shell
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 53
Vulnerability Type: Remote payload retrieval and execution
Risk Level: HighVulnerable Code:
bash # Method 2: Install through the official installation script curl -fsSL https://raw.githubusercontent.com/umeng/umeng-cli/main/scripts/install.sh | shTechnical Analysis
The installation command retrieves a shell script from the mutable
mainbranch of an external GitHub repository and pipes it directly intosh. The downloaded content is not pinned to a release or immutable commit, and no checksum, cryptographic signature, or manual inspection step is required before execution.Although the repository matches the project homepage declared by the Skill, that association does not guarantee that future content served from the URL will remain trustworthy. Compromise of the upstream repository, maintainer account, release process, DNS or network trust chain could turn this command into an arbitrary code-execution channel after the Skill itself has already been reviewed.
The installation is only a prerequisite for the declared read-only analytics functionality. Immediate execution of mutable remote code is therefore not the minimum privilege or safest installation mechanism necessary to provide that functionality.
Attack Path
- An attacker compromises the upstream repository, a maintainer account, or another component capable of changing
scripts/install.shon themainbranch. - The attacker adds arbitrary shell commands to the installation script.
- A user or AI Agent follows the installation instructions in
SKILL.md. curlretrieves the attacker-controlled version of the script.- The pipe sends the response directly to
shwithout an integrity or review boundary. - The malicious commands execute with all permissions held by the user running the installation.
Impact Assessment
Successful exploitation provide ...[truncated 582 chars]
- An attacker compromises the upstream repository, a maintainer account, or another component capable of changing
- Remediation
View remediation
Remediation Suggestions
- Remove the direct
curl | shinstallation method. - Prefer installation from a version-pinned package release through a trusted package registry.
- If a standalone installer is necessary:
- Download it to a local file rather than piping it into a shell.
- Pin the download to an immutable release or commit.
- Publish and verify a cryptographic checksum or signature.
- Permit inspection of the downloaded script before execution.
- Execute it without elevated privileges unless a documented operation strictly requires elevation.
- Document all files, permissions, network destinations, and credential stores affected by installation.
- Recommend isolated installation or execution where practical.
- Remove the direct
