T03 · Remote Payload Retrieval and Execution
- Location
SKILL.md:61- Finding
Unverified Precompiled Executables Downloaded from an External Release
- Content
View full analysis
- Remediation
View remediation
douyin-dl" | sha256sum --check - ``` 3. Digitally sign release artifacts or checksums with a documented signing identity, such as Sigstore/Cosign, and provide explicit signature-verification commands. 4. Generate and publish build provenance using a protected CI/CD pipeline. Pin all build dependencies and restrict who can approve releases. 5. Prefer reproducible builds so users can compare locally built artifacts with published binaries. 6. Download to a temporary staging location, verify the artifact, and only then atomically install it into `~/.local/bin`. 7. Document the security behavior of command-line hot updates. Updates should require explicit consent and must undergo the same signature and integrity checks. 8. Avoid recommending execution by privileged users and clearly state that the binaries should run with the minimum necessary permissions. ]]>
