T03 · Remote Payload Retrieval and Execution
- Location
QUICKSTART.md:14- Finding
Automatic Execution of Mutable Remote Installation Scripts
- Content
View full analysis
Steps marked with **[AUTO]** can be executed without asking the user. > Steps marked with **[ASK]** require user input before proceeding. ## One-Line Install [AUTO] **macOS / Linux** — installs the Python package and MCP server binary in one step: ```bash curl -fsSL https://raw.githubusercontent.com/toddpan/feyagate-skill/main/scripts/install.sh | bash ``` **Windows (PowerShell):** ```powershell iwr -useb https://raw.githubusercontent.com/toddpan/feyagate-skill/main/scripts/install.ps1 | iex ``` ``` ### Technical Analysis The installation instructions download mutable content from the `main` branch of a personal GitHub repository and immediately pass it to Bash or PowerShell. The effective code executed on a user's system can therefore change after this Skill has been reviewed. Neither installation path pins an immutable commit, verifies a cryptographic signature, checks a published digest, nor lets the user inspect the downloaded file before execution. The `-s`/`-fsSL` and `-useb` options also make this a streamlined, noninteractive execution flow. The risk is amplified by labeling the installation step as `[AUTO]` and explicitly stating that an AI assistant may execute it without asking the user. Installation of a smart-home gateway may be legitimate, but unattended execution of an unverified remote script is not the minimum privilege necessary to perform that installation. The actual remote scripts are not included in the audited artifact. Consequently, their current or future behavior—including downloaded binaries, filesystem modifications, persistence, credential access, and network activity—cannot be verified by this audit. ### Attack Path 1. An attacker compromises the GitHub account, repository, branch, or content delivery pat ...[truncated 1181 chars]- Remediation
View remediation
" sha256sum -c install.sh.sha256 less install.sh bash install.sh ``` 7. Apply the equivalent download, signature verification, inspection, and execution separation on Windows. 8. Include the installer source in the audited Skill artifact or link it to an immutable revision so reviewers can verify its behavior. 9. Document every file, executable, service, and network endpoint the installer creates or contacts. ]]>
