T03 · Remote Payload Retrieval and Execution
- Location
references/runtime-requirements.md:35- Finding
Automatic Execution of Mutable Code Retrieved Through Untrusted Mirrors
- Content
View full analysis
git clone https://gh-proxy.org/https://github.com/dreammis/social-auto-upload.git git clone https://gh-proxy.com/https://github.com/dreammis/social-auto-upload.git git clone https://hub.gitmirror.com/https://github.com/dreammis/social-auto-upload.git ``` From `references/runtime-requirements.md:81-100`: ```bash cd copy conf.example.py conf.py cp conf.example.py conf.py uv sync --python 3.12 uv run --project python sau_cli.py --help ``` ### Technical Analysis The Skill requires the agent to clone the `social-auto-upload` repository from a mutable default branch and then install its dependencies and execute its Python entry point. No immutable Git commit, signed tag, trusted checksum, or repository signature is verified before execution. If direct GitHub access fails, the instructions require automatic retries through several third-party services. One fallback is a repository under a different owner: ```text Declared upstream: github.com/dreammis/social-auto-upload Fallback source: gitee.com/lonycn/social-auto-upload ``` This is not merely an alternate transport endpoint. It is a separately controlled repository whose equivalence to the declared upstream is not established. The proxy services also terminate or relay retrieval through additional in ...[truncated 2570 chars]- Remediation
View remediation
