T03 · Remote Payload Retrieval and Execution
- Location
install.sh:39- Finding
Unverified Remote Executable Download and Root-Level Installation
- Content
View full analysis
/dev/null || true fi tar xvf "trojan-${TROJAN_VERSION}-linux-amd64.tar.xz" > /dev/null 2>&1 mv trojan "$TROJAN_DIR" chmod +x "$TROJAN_DIR/trojan" ``` ### Technical Analysis The root-run installer retrieves a precompiled executable archive from a GitHub release and installs it without validating a cryptographic signature or pinned checksum. The URL points to the declared upstream `trojan-gfw` GitHub organization rather than a paste site or obvious personal fork, but HTTPS alone does not establish that the downloaded artifact matches the version reviewed by the Skill auditor. The script also trusts any preexisting archive at `/usr/src/trojan-1.16.0-linux-amd64.tar.xz`. A local attacker or an earlier compromised process able to create that file can bypass the download entirely. The archive is extracted by a root process without first validating its contents or paths. This behavior allows the effective executable payload to differ after the Skill package has been reviewed. ### Attack Path 1. An attacker compromises the upstream release, its publishing account, the delivery trust chain, or places a malicious archive at the expected `/usr/src` path before installation. 2. The administrator runs `sudo ./install.sh`. 3. The script either download ...[truncated 889 chars]- Remediation
View remediation
