News for hackers. Stuff that matters.
Re:Mini Shai-Hulud Strikes Again: 314 npm Packages Compromised by zahlman on Tuesday May 19, 2026 @12:08PM (#48195234)
> and trust that NPM at least gets their "you can't republish to an old version" bare-minimum constraint right?

... Does NPM not create full lockfiles, with hashes and pinned transitive dependencies and everything?

Re:Mini Shai-Hulud Strikes Again: 314 npm Packages Compromised by btown on Tuesday May 19, 2026 @01:42PM (#48196550)
Yes, and the problem here is that most projects have automated systems that automatically update those lockfiles on every upstream release of a library, under an assumption that minor releases are either security patches or bugfixes that would immediately be useful to the consuming project.

IMO this is built on a pre-ShaiHulud, pre-AI set of assumptions, and should be evaluated from first principles with today's security situation.

Re:Mini Shai-Hulud Strikes Again: 314 npm Packages Compromised by zahlman on Wednesday May 20, 2026 @09:07AM (#48207062)
My point was the "with hashes" part. You aren't in fact "trusting" NPM to ensure that old versions aren't replaced if the package installer is verifying the hash.
Re:Mini Shai-Hulud Strikes Again: 314 npm Packages Compromised by esafak on Tuesday May 19, 2026 @02:33PM (#48197348)