T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:55- Finding
Unverified Remote Shell Script Retrieved from a Mutable Branch and Executed
- Content
View full analysis
- Remediation
View remediation
/publish.sh" echo " publish.sh" | sha256sum --check - bash publish.sh ``` 4. Prefer signed release artifacts and verify the maintainer's cryptographic signature against a separately established trusted key. 5. Review the script locally before execution and expose its source as part of the audited Skill. 6. Use a fine-grained GitHub token restricted to the specific target repository and only the permissions needed to create releases and upload assets. 7. Avoid broadly scoped classic Personal Access Tokens. Use short-lived credentials where supported and revoke or rotate them after suspected exposure. 8. Prevent the release script from reading unrelated files or credentials, and run it in an isolated CI job or restricted container with access only to the required project files. 9. Configure branch protection, mandatory review, signed commits, and restricted write access for the repository hosting any release automation. ]]>
