T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:14- Finding
Remote Installer Downloaded and Executed Without Independent Verification
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:14
Vulnerability Type: Remote payload retrieval and execution
Risk Level: CriticalVulnerable Code:
bash curl -fsSL https://cli.inference.sh | sh && infsh loginTechnical Analysis
The Quick Start instructions pipe content retrieved from a mutable external URL directly into a shell. The user cannot inspect the downloaded installer before execution, and the command does not pin an installer version, validate the installer against a trusted cryptographic signature, or verify a locally downloaded file before running it.
The documentation states that the remote installer verifies the checksum of the CLI binary it downloads. This does not establish the integrity of the installer itself. If the installer endpoint or its deployment infrastructure is compromised, the returned script can change its own verification behavior, select a malicious binary, or execute unrelated commands before any binary verification occurs.
Although installing a CLI supports the Skill's declared functionality, immediate execution of mutable remote code is not the minimum-risk installation mechanism. The command runs the installer with all permissions available to the invoking user and then starts an authentication flow.
Attack Path
- An attacker compromises the installer endpoint, its hosting infrastructure, or another relevant upstream delivery component.
- The attacker changes the content returned by
https://cli.inference.sh. - A user or agent follows the documented Quick Start command.
curlretrieves the attacker-controlled script.- The pipe sends the response directly to
sh, which executes it without inspection or independent integrity validation. - The script performs arbitrary operations using the invoking user's permissions.
- The attacker may access user-readable data, modify user-owned files, steal available credentials, install additi ...[truncated 787 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the
curl | shinstallation pattern. - Pin the CLI to a specific reviewed release rather than retrieving an implicitly current version.
- Download the release artifact to a local file without executing it.
- Verify the artifact using a cryptographic signature or a pinned SHA-256 digest obtained through an independent trusted channel.
- Abort installation if verification fails.
- Execute or install the artifact only after successful verification and, where practical, explicit user approval.
- Keep
infsh loginseparate from installation so authentication is a distinct, user-confirmed action. - Publish reproducible release metadata and signed checksums over a separately secured channel.
- Avoid recommending elevated privileges; install into a user-controlled location with only the permissions required by the CLI.
- Remove the
