GitHub Tightens npm Publishing After Flaw Left 1,500+ Packages Vulnerable to Hijacking

GitHub has implemented changes to npm's trusted publishing mechanism after a vulnerability was discovered that allowed attackers to hijack over 1,500 packages by exploiting repository name reuse (slug reuse). The flaw, named SlugFest by Bloom Security, stemmed from npm's reliance on mutable repository slugs rather than immutable IDs for trusted publishing configurations, enabling attackers to claim abandoned repository paths and publish malicious versions of legitimate packages without credential theft. The attack could lead to large-scale supply chain compromises, especially when combined with AI agents that automatically pull dependencies without human oversight. GitHub now expires unvalidated trusted publishing configurations after 48 hours and requires re-validation upon repository changes to mitigate the risk.

AI-extracted · verify before operational use