T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:130- Finding
Unpinned Remote Binary Retrieval and Execution
- Content
View full analysis
mcp.log 2>&1 & echo $! > mcp.pid ``` ### Technical Analysis The deployment procedure downloads the current release artifact matching a mutable filename from an external GitHub repository and immediately extracts and executes its binaries. It does not pin an immutable release version or commit, verify a cryptographic checksum, validate a digital signature, or build from audited source. Consequently, the code executed by users may differ from the artifact that existed when this Skill was reviewed. Compromise of the upstream repository, release account, release workflow, or distributed archive would allow an attacker to substitute arbitrary executable code. Running the login binary is particularly sensitive because it participates in account authentication and may have access to Xiaohongshu session material. ### Attack Path 1. An attacker compromises the upstream repository, release credentials, or release pipeline. 2. The attacker replaces the matching release archive with a modified archive containing malicious binaries. 3. A user follows the Skill instructions and runs `gh release download` without selecting an immutable version. 4. The archive is extracted without integrity or authenticity verification. 5. The user executes the modified login binary and starts the modified ...[truncated 718 chars]- Remediation
View remediation
