Supply-chain attacks through history: 56 OSS projects, 59 incidents

This title was summarized by AI from the post below.

🔗 𝐀𝐥𝐥 𝐤𝐧𝐨𝐰𝐧 𝐬𝐮𝐩𝐩𝐥𝐲-𝐜𝐡𝐚𝐢𝐧 𝐚𝐭𝐭𝐚𝐜𝐤𝐬 𝐭𝐡𝐫𝐨𝐮𝐠𝐡 𝐡𝐢𝐬𝐭𝐨𝐫𝐲 thomas strömberg has curated a dataset on software supply-chain attacks. 56 OSS projects, 59 incidents. Criteria: when an open-source project or commercial product distributed malware knowingly or unknowingly. One YAML file per incident. https://lnkd.in/gvT3r_R6 #cybersecurity

  • chart, pie chart

Incredible dataset! thanks for sharing this, Clint. What stood out to me is how over half of the incidents involve compromise at the distribution layer, not the codebase itself. It reinforces how modern AppSec needs to go beyond SAST/DAST and look at the entire software delivery pipeline: CD configs, artifact storage, package managers, even post-release integrity checks. It also highlights the urgent need for attestation and provenance in CI/CD. Signing isn’t just a compliance checkbox anymore, it’s the bare minimum to detect tampering across build and deploy stages. Kudos to Thomas for the structured YAML format too, perfect for feeding into threat modeling and detection pipelines.

To view or add a comment, sign in

Explore content categories