Re:Self Propagating NPM Malware Compromises over 40 Packages
by benoau on Tuesday September 16, 2025 @08:30PM
(#45270082)
I like to pin specific versions in my package.json so dependencies don't change without manual steps, and use "npm ci" to install specifically the versions in package-lock.json. My CI runs "npm audit" which will raise the alarms if a vulnerability emerges in those packages. With everything essentially frozen there either is malware within it, or there is not going to be, and the age of the packages softly implies there is not.
[ Parent
| on HN ]
There are no comments on this comment yet.