T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:33- Finding
Unverified Remote Installer Is Downloaded and Executed Through Bash
- Content
View full analysis
Vulnerability Details
File Location:
SKILL.md:33
Vulnerability Type:T03: Remote Payload Retrieval and Execution
Risk Level: HighComplete Code Snippet:
bash curl -fsSL https://skills.video/cli/install.sh | bashTechnical Analysis
The installation instructions pipe a remotely retrieved shell script directly into Bash. The script is not included in the audited project, so its effective behavior cannot be reviewed from the repository and may change at any time without changing this Skill.
The command provides no version pinning, cryptographic signature or checksum verification, local inspection step, or explicit user approval before execution. HTTPS protects the connection in ordinary circumstances but does not establish that every future version of the remote installer is trustworthy. Compromise of the remote website, hosting account, CDN, DNS path, TLS infrastructure, or release process could turn the installer into an arbitrary payload delivery mechanism.
Installing the CLI is relevant to the Skill's declared image and video generation functionality. However, immediate execution of mutable network content is not the least-privileged installation method. A pinned and independently verified package or release artifact would reduce the required trust and execution scope.
Attack Path
- The Skill is loaded for an image or video generation request.
- The
skillsvideoexecutable is not present on the user's system. - Following the mandatory installation workflow, the agent runs the documented
curl | bashcommand. - An attacker who controls or compromises the remote installer delivery path modifies
install.sh. curlstreams the attacker-controlled content directly to Bash without integrity verification or prior inspection.- Bash executes the payload with the permissions and environment of the agent process.
Impact Assessment
A malicious installer could execute arb ...[truncated 730 chars]
- Remediation
View remediation
Remediation Suggestions
- Replace the direct
curl | bashpipeline with a pinned, auditable package or versioned release artifact. - Publish cryptographic checksums and preferably signed release metadata through an independently verifiable channel.
- Download the installer or artifact to a local file first, then verify its signature or checksum before execution.
- Allow the user or agent to inspect the downloaded script and require explicit user approval before running it.
- Avoid requesting administrator privileges unless a specific installation step strictly requires them; prefer a user-scoped installation directory.
- Pin the expected installer or CLI version rather than silently executing the latest mutable server response.
- Document the files, configuration, credentials, and network endpoints used by the installer and provide removal instructions.
- If a shell installer remains necessary, fail closed when integrity verification is unavailable or unsuccessful.
- Replace the direct
