[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fUBfBNh8MBQonSdQBdpnFkHHLPr1FQD4KH0FdTKCgVOE":3},{"lesson":4},{"id":5,"slug":6,"article_id":7,"title":8,"body":9,"prevention":10,"framework_refs":11,"framework_notes":17,"status":23,"created_at":24,"published_at":25,"article":26,"tags":30,"podcasts":43,"controls":50},"a3f50824-4ffd-454f-b9c2-52de10f7b2e5","massive-npm-package-poisoning-attack-compromises-developer-credentials","b0cdc22d-65a4-4a05-9716-c78cb04f2def","Massive npm Package Poisoning Attack Compromises Developer Credentials","The Shai-Hulud malware campaign successfully compromised 639 malicious npm package versions by exploiting trust in the package ecosystem, particularly targeting popular visualization libraries in the @antv ecosystem. The attackers demonstrated sophisticated techniques including credential theft across multiple platforms (GitHub, npm, cloud services, Kubernetes, CI\u002FCD), evasion through P2P networks, and even forging Sigstore provenance attestations to appear legitimate. This attack highlights the critical vulnerability in software supply chains where developers automatically trust and install packages, making it essential for organizations to implement rigorous package validation and monitoring processes.","**Immediate actions:**\n- Audit all npm packages in use and check against known compromised package lists\n- Implement package pinning and lock file verification in all projects\n- Rotate all GitHub, npm, cloud, and CI\u002FCD credentials as a precautionary measure\n\n**Long-term improvements:**\n- Deploy automated dependency scanning tools with real-time alerts for suspicious packages\n- Establish internal package repositories with security validation before allowing external packages\n- Implement zero-trust principles for package installations requiring explicit approval for new dependencies\n\n**Detection measures:**\n- Monitor network traffic for unusual P2P communications and unauthorized GitHub repository access\n- Set up alerts for unexpected VS Code and IDE configuration changes\n- Enable comprehensive logging of package installation and credential usage activities",[12,13,14,15,16],"CIS Control 2.1","NIST SP 800-161","NIST SSDF","CIS Control 11.2","OWASP SCVS",{"NIST SSDF":18,"OWASP SCVS":19,"CIS Control 2.1":20,"NIST SP 800-161":21,"CIS Control 11.2":22},"The SSDF calls for verifying third-party components and protecting build credentials, the targets of Shai-Hulud.","Software component verification standards help organisations check package integrity and provenance, though forged Sigstore attestations show provenance alone is not enough.","A detailed software inventory, including npm dependencies, lets teams quickly find projects pulling any of the 639 poisoned package versions.","Supply chain risk management treats npm packages as supplier inputs that need vetting, not blind trust.","Automated backups let teams restore clean build systems and repositories after credential-stealing malware compromises them.","published","2026-05-22T05:42:42.954479+00:00","2026-05-22T05:42:41.363357+00:00",{"id":7,"url":27,"slug":28,"title":29},"https:\u002F\u002Fwww.bleepingcomputer.com\u002Fnews\u002Fsecurity\u002Fnew-shai-hulud-malware-wave-compromises-600-npm-packages\u002F","new-shai-hulud-malware-wave-compromises-600-npm-packages-629679","New Shai-Hulud malware wave compromises 600 npm packages",[31,37],{"id":32,"name":33,"slug":34,"description":35,"color":36},"05757c8d-6b93-4194-b35d-7359e7d33b0e","Vulnerability Management","vulnerability-management","Missing scans, no risk prioritization","#fb923c",{"id":38,"name":39,"slug":40,"description":41,"color":42},"f0c2a0af-58aa-4128-87c9-6acd30f2dc48","Supply Chain","supply-chain","Third-party risk, compromised dependencies","#8b5cf6",[44],{"id":45,"date":46,"edition":47,"title":48,"audio_url":49},"842c1cf3-ee01-4a35-8282-685ec1422d58","2026-05-20","morning","ThreatNoir Morning Brief — May 20","https:\u002F\u002Fcdn.threatnoir.com\u002Fpodcasts\u002F2026-05-20\u002Fthreatnoir-morning-brief-2026-05-20.mp3",[51,55,59],{"slug":52,"name":53,"problem":54},"secrets-management","Secrets management","API keys, tokens and passwords stop leaking from code, chat and configuration files.",{"slug":56,"name":57,"problem":58},"security-monitoring-siem","Security monitoring (SIEM)","Logs from everywhere end up in one place, with alerts that someone actually sees.",{"slug":60,"name":61,"problem":62},"software-supply-chain","Software supply chain security","Malicious and vulnerable open-source packages are caught before they ship."]