T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:70- Finding
Unverified Remote Bash Installer Execution
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 70
Vulnerability Type: Remote payload retrieval and execution through a shell pipeline
Risk Level: HighVulnerable Code
bash curl -LsSf https://code.kimi.com/install.sh | bashTechnical Analysis
This installation instruction downloads a mutable shell script from an external server and immediately sends it to Bash. The payload is neither pinned to a specific version nor authenticated using a cryptographic signature or published checksum. It is also not saved for inspection before execution.
HTTPS provides transport protection but does not establish that the retrieved script is safe. If the hosting server, DNS resolution, publishing credentials, or upstream deployment process is compromised, the command will execute attacker-controlled shell instructions. Because the effective payload remains external to the audited project, its behavior can change after review without any modification to
SKILL.md.Direct remote execution is not required for the Skill's declared documentation-assistance functionality and exceeds the minimum behavior needed to answer installation questions.
Attack Path
- A user asks the Skill how to install Kimi CLI.
- The Skill reproduces the installation command from its quick reference.
- The user runs the command in a terminal.
- Bash retrieves the current script controlled by
code.kimi.com. - If the remote distribution channel has been compromised or the script has been maliciously replaced, Bash executes the substituted payload without review or integrity verification.
- The payload performs arbitrary operations using the invoking user's permissions.
Impact Assessment
A substituted installer can execute arbitrary shell commands with the privileges of the user running it. This may permit access to source code, local files, environment variables, API tokens, SSH material, and other credentials a ...[truncated 442 chars]
- Remediation
View remediation
Remediation Suggestions
Remove the pipe-to-shell installation instruction. Prefer a trusted package manager with a version-pinned release, such as a reviewed and explicitly versioned
uvpackage installation.If a standalone installer must be offered:
- Download it to a non-executable file rather than piping it directly into Bash.
- Pin the download to an immutable release version.
- Publish and verify a SHA-256 checksum over a separate authenticated channel.
- Prefer publisher signature verification over checksums alone.
- Allow the user to inspect the script before execution.
- Execute it without administrative privileges unless a documented operation strictly requires elevation.
- Document the files, network access, and configuration changes the installer performs.
