CLAIM-2026-08-06-04

The malicious versions carried valid provenance attestations: the attacker compromised the maintainer's GitHub account, pushed poisoned commits and tags, and let the projects' own release workflows publish via OIDC trusted publishing, so the attestation proved build origin rather than authorisation.

Why it matters

Provenance and SLSA attestation are widely deployed as the control for exactly this attack. This shows the attestation was valid and still did not help, because it attests build origin rather than authorisation.

Sources

• stepsecurit2026chaindrop