A Valid Signature Signed Malware: What the Agent Framework Certificate Proved
Malicious versions of Microsoft's Agent Framework were reportedly published to PyPI, with reporting tying the compromise to a release-pipeline certificate. This video walks through what that certificate actually attests to: which CI provider minted the identity, which repository and workflow file ran, which commit the build started from, and the artifact digest that got signed. It also covers what it does not attest to: that the build runner was clean, that the artifact's contents match the repository source, or that the code behaves benignly. The defensive takeaway is narrow and concrete: verify attestations at install time instead of treating them as a compliance checkbox, pin third-party actions to a commit hash rather than a mutable tag, keep the id-token permission on the publish job alone rather than on the build job, gate publishing behind a protected environment, and avoid pulling a full dev dependency tree inside the job that builds the artifact. Nothing here is a working exploit; it is a lab-scoped look at workflow configuration and where the trust boundary sits. Details of the incident itself are drawn from secondary reporting, and the post is explicit about which parts are inference versus confirmed. Affected version ranges should come from the vendor advisory, not from this video. Full write-up: https://hackyjs.com/posts/how-a-release-pipeline-certificate-let-credential-stealing-wheels-ship-as-microsoft-agent-framework