News for hackers. Stuff that matters.
Re:Self Propagating NPM Malware Compromises over 40 Packages by koakuma-chan on Tuesday September 16, 2025 @08:04AM (#45261097)
Until you need to write JavaScript?
Re:Self Propagating NPM Malware Compromises over 40 Packages by ehnto on Tuesday September 16, 2025 @08:10AM (#45261161)
But that's the neat part, you don't!
Re:Self Propagating NPM Malware Compromises over 40 Packages by koakuma-chan on Tuesday September 16, 2025 @08:11AM (#45261170)
Until you have to.
Re:Self Propagating NPM Malware Compromises over 40 Packages by speed_spread on Tuesday September 16, 2025 @09:20AM (#45261880)
The only way to win is not to play.
Re:Self Propagating NPM Malware Compromises over 40 Packages by koakuma-chan on Tuesday September 16, 2025 @09:53AM (#45262311)
Let me quit my job real quick. The endgame is probably becoming a monk, no kidding.
Re:Self Propagating NPM Malware Compromises over 40 Packages by joquarky on Wednesday September 17, 2025 @01:16AM (#45271982)
I considered becoming a Zen monk, but then I gave up the desire.
Re:Self Propagating NPM Malware Compromises over 40 Packages by baq on Tuesday September 16, 2025 @08:09AM (#45261143)
Which should be much less than what’s customary?
Re:Self Propagating NPM Malware Compromises over 40 Packages by bdcravens on Tuesday September 16, 2025 @08:19AM (#45261240)
Then write it. Javascript itself isn't the problem, naive third-party dependencies are.
Re:Self Propagating NPM Malware Compromises over 40 Packages by pixl97 on Tuesday September 16, 2025 @10:56AM (#45263178)
Developers are perfectly fine with writing insecure JS all by themselves.
Re:Self Propagating NPM Malware Compromises over 40 Packages by yawaramin on Wednesday September 17, 2025 @09:11PM (#45283673)
But developers don't typically write malware to deploy on their production systems.