T03 · Remote Payload Retrieval and Execution
- Location
README.md:22- Finding
Remote installation script is executed directly without integrity verification
- Content
View full analysis
--base https://vigilath.cn ``` Equivalent installation instructions also appear in `install.sh:5-10`. ### Technical Analysis The documented installation procedure streams a remote HTTP response directly into Bash. The downloaded script is not pinned to a release version, inspected before execution, verified against a cryptographic checksum, or authenticated with a digital signature. Consequently, the effective installer payload can change after this repository has been reviewed. Trust in the checked-in `install.sh` does not establish trust in the content that will later be served from the documented URL. HTTPS protects data in transit but does not protect against compromise of the hosting account, origin server, deployment pipeline, DNS configuration, or TLS termination infrastructure. ### Attack Path 1. An attacker compromises the hosting server, deployment pipeline, or account controlling `vigilath.cn`. 2. The attacker replaces the hosted `install.sh` response with a malicious shell payload. 3. A user follows the installation instructions. 4. `curl` downloads the modified response. 5. Bash executes the response immediately with the privileges of the installing user. 6. The payload can access the user's files, credentials, Agent configuration, and other resources available to that account. ### Impact Assessment Successful exploitation provides arbitrary shell command execution as the installing user. The affected scope can include: - Files and credentials accessible to the current user. - Agent Skill directories and configuration. - ...[truncated 387 chars]- Remediation
View remediation
