T03 · Remote Payload Retrieval and Execution
Error
- Location
README.md:94- Finding
Unpinned Remote Repository Is Cloned and Immediately Executed
- Content
View full analysis
- Remediation
View remediation
``` The full commit hash should be published through a trusted release channel. 3. **Publish signed, versioned releases.** Prefer a tagged release whose Git tag or commit is cryptographically signed and whose signer identity is documented. 4. **Publish and verify checksums.** If distributing an archive, provide a SHA-256 digest through a separately protected channel and require verification before extraction or execution. 5. **Require installer inspection.** Document commands such as: ```bash sed -n '1,240p' install_skill.sh ``` Only execute the script after verification. 6. **Prefer a non-executable installation path.** Since the audited Skill consists of text resources and standard-library Python scripts, provide explicit copy commands from a verified local checkout rather than relying on an installer. 7. **Minimize installer permissions.** The installer should: - Never invoke `sudo`. - Write only to the selected Skill directory. - Avoid modifying shell startup files or unrelated agent configuration. - Avoid reading credentials. - Fail before making changes if destination paths are unexpected. 8. **Add release provenance.** Use a reproducible release process and publish build provenance or attestations so users can establish that the distributed artifact corresponds to the reviewed source. 9. **Document uninstall and changed files.** Clearly enumerate every path created or modified by installation so users can review and reverse the operation. ]]>