T03 · Remote Payload Retrieval and Execution
- Location
scripts/install.sh:181- Finding
Remote Script Execution Recommended Through a curl-to-shell Pipeline
- Content
View full analysis
/dev/null; then log_ok "npx: $(npx --version 2>&1)" else log_warn "未找到 npx,Wind AIFin Market Skill 将跳过。安装: curl -fsSL https://fnm.vercel.app/install | bash" fi ``` ### Technical Analysis The installer recommends downloading a mutable remote script and piping it directly into `bash`. Although this command is printed as an installation instruction rather than automatically executed by `install.sh`, following the documented instruction executes whatever content the remote endpoint serves at that moment. There is no version pinning, cryptographic checksum, signature verification, local review step, or immutable artifact reference. The effective payload can therefore change after this Skill has been audited. HTTPS protects transport under normal conditions but does not protect against compromise of the upstream site, its hosting account, its release process, or a trusted certificate authority. This behavior is not necessary for the Skill's stock-analysis and report-generation functions. Node.js installation should remain a separately controlled prerequisite. ### Attack Path 1. An attacker compromises the remote installer endpoint, its hosting infrastructure, or its deployment credentials. 2. The attacker replaces the expected installer with a malicious shell payload. 3. A user runs `scripts/install.sh` on a system without `npx`. 4. The installer prints the `curl -fsSL ... | bash` command as the recommended remediation. 5. The user follows that instruction. 6. The malicious response is executed immediately by `bash` with the user's privileges. 7. The payload can access user-readable files, alter shell configuration, install persistence, or compromise the Agent environment. ### Impact Assessment Successful exploitation provides ...[truncated 518 chars]- Remediation
View remediation
