T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:14- Finding
Unverified Remote Installer Executed Directly by the Shell
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md, line 14
Vulnerability Type: Remote payload retrieval and execution
Risk Level: HighVulnerable Code:
bash curl -fsSL https://cli.inference.sh | sh && infsh loginTechnical Analysis
The quick-start procedure retrieves a mutable shell script from
https://cli.inference.shand pipes it directly intosh. This grants the current remote response arbitrary command-execution capability under the invoking user's account before the user can inspect or independently verify it.Although the install note states that the script downloads a matching binary and verifies its SHA-256 checksum, this does not establish a secure trust boundary. The bootstrap script itself is neither version-pinned nor checked against a locally specified digest or trusted signature. Because that same script controls the download URL and verification procedure, a compromised or malicious response could remove, bypass, or replace those checks.
Installing a client is relevant to the Skill's image-generation functionality, but executing an unreviewed and mutable installer is not the minimum privilege or minimum trust mechanism required. A version-pinned artifact with independent verification would provide the needed functionality with less supply-chain risk.
Attack Path
- A user or Agent follows the documented quick-start command.
- The command contacts
cli.inference.shand accepts the server's current response without version pinning. - An attacker compromises the distribution domain, hosting account, deployment pipeline, or another trusted delivery component and substitutes a malicious shell response.
shexecutes that response immediately with the permissions of the invoking user.- The payload can access resources available to that account, alter files or tools, collect credentials, or install additional components.
- If the installer appears to complete normall ...[truncated 927 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove the
curl | shinstallation pipeline from the quick-start instructions. - Pin the CLI to a specific immutable version rather than downloading the latest installer or binary.
- Download the artifact to a local file as a separate operation.
- Publish the expected SHA-256 digest in version-controlled Skill documentation and verify it locally before execution. Do not rely solely on a checksum selected or downloaded by the same installer.
- Prefer signed release artifacts and verify the signature against a pinned, independently distributed public key.
- Provide transparent manual installation commands showing the exact source, destination, and permissions of every installed file.
- Run installation without elevated privileges and use a user-owned directory with narrowly scoped permissions.
- Keep
infsh loginas a separate, explicit command after installation and verification so authentication never occurs automatically through a newly downloaded executable. - Where possible, use a trusted package repository with version locking, integrity metadata, and reproducible release provenance.
- Pin versions in the optional
npx skills addexamples as additional supply-chain hardening.
- Remove the
