T03 · Remote Payload Retrieval and Execution
- Location
references/deploy.md:16- Finding
Unpinned and Unverified Third-Party Binary Download and Execution
- Content
View full analysis
mcp.log 2>&1 & echo $! > mcp.pid ``` ### Technical Analysis The deployment procedure downloads a precompiled executable from a third-party GitHub release and runs it with the current user's privileges. The command does not pin a reviewed release tag, commit, or immutable artifact identifier. It also performs no checksum, signature, provenance, or publisher verification before extraction and execution. Consequently, the effective executable payload can change after the Skill documentation has been reviewed. A compromised upstream maintainer account, release workflow, repository, or downloadable release asset could substitute malicious code. The use of GitHub as the disclosed source does not by itself establish artifact integrity. Extracting the archive before validating its contents also creates an additional archive-safety concern. A malicious archive could potentially contain unexpected paths or files in addition to the documented executables. ### Attack Path 1. An attacker compromises the upstream repository, maintainer credentials, release pipeline, or release asset. 2. The attacker publishes or replaces an artifact matching the broad filename pattern used by the deployment command. 3. A user ...[truncated 1251 chars]- Remediation
View remediation
