News for hackers. Stuff that matters.
Re:Self Propagating NPM Malware Compromises over 40 Packages by m4r71n on Tuesday September 16, 2025 @09:58AM (#45262368)
Since so many vendors discovered these packages seemingly independently, you'd think that they would share those mechanisms with NPM itself so that those packages would never be published in the first place. But I guess that removes their ability to sell an "early alert" mechanism through their offerings...
Re:Self Propagating NPM Malware Compromises over 40 Packages by progbits on Tuesday September 16, 2025 @10:19AM (#45262594)
NPM is owned by github/microsoft. I'm sure they could afford to buy one of these products or just build their own, but clearly security is not a thing they care about.
Re:Self Propagating NPM Malware Compromises over 40 Packages by codazoda on Tuesday September 16, 2025 @10:31AM (#45262772)
Somehow I didn't realize GitHub purchased npm in 2020. GitHub is the second word on npmjs.org. How did I not notice?
Re:Self Propagating NPM Malware Compromises over 40 Packages by octo888 on Tuesday September 16, 2025 @11:12AM (#45263412)
Microsoft: GitHub, NPM, typescript, VS Code, OpenAI, Playwright

A lot of fingers in a lot pies

Re:Self Propagating NPM Malware Compromises over 40 Packages by LPisGood on Tuesday September 16, 2025 @02:34PM (#45266053)
I believe someone working there once said “Developers, developers, developers, developers, developers!
Re:Self Propagating NPM Malware Compromises over 40 Packages by philipwhiuk on Tuesday September 16, 2025 @04:48PM (#45267822)
Also LinkedIn
Re:Self Propagating NPM Malware Compromises over 40 Packages by foobarbecue on Tuesday September 16, 2025 @11:04AM (#45263297)
Can't help noticing, in the original article:

> The entire attack design assumes Linux or macOS execution environments, checking for os.platform() === 'linux' || 'darwin'. It deliberately skips Windows systems

If I were the conspiracy-minded sort I might jump to some wild conclusions here.

Re:Self Propagating NPM Malware Compromises over 40 Packages by acomjean on Tuesday September 16, 2025 @12:53PM (#45264766)
I’m using windows again. By default windows has “power shell” which is not at all like bash and is (how do I say this diplomatically)… wanting.

I mean it says something the developed the Linux Subsystem for Windows, but it’s an optional install.

Re:Self Propagating NPM Malware Compromises over 40 Packages by jahsome on Tuesday September 16, 2025 @02:26PM (#45265934)
What dont you like about powershell?

I'm a die hard linux user, and some years ago took a windows gig on a whim. I find powershell fantastic and the only thing that makes my role bearable. Now, one of the first things i install on Linux is powershell.

Re:Self Propagating NPM Malware Compromises over 40 Packages by philipwhiuk on Tuesday September 16, 2025 @04:49PM (#45267838)
The awk equivalents in power-shell are horrific.
Re:Self Propagating NPM Malware Compromises over 40 Packages by jahsome on Wednesday September 17, 2025 @12:40AM (#45271737)
You don't find awk itself horrific in its own way?
Re:Self Propagating NPM Malware Compromises over 40 Packages by stockresearcher on Tuesday September 16, 2025 @03:30PM (#45266823)
I watched an interview with Jeff Snover once and he said that they tried to make a unixy bash-like shell a few times and decided it was never going to fit in Windows. So they went a different way and took a lot of inspiration from OpenVMS.

So don’t expect PowerShell to be like a UNIX shell. It isn’t, and wasn’t meant to be one. It’s different, on purpose :)

Re:Self Propagating NPM Malware Compromises over 40 Packages by vips7L on Tuesday September 16, 2025 @04:34PM (#45267625)
Powershell is amazing. Just don't expect it to be posix. Using objects and structured data is leagues better than string parsing in posix shells imo.
Re:Self Propagating NPM Malware Compromises over 40 Packages by chatmasta on Tuesday September 16, 2025 @02:42PM (#45266148)
Whoever made the exploit probably doesn’t use windows.
Re:Self Propagating NPM Malware Compromises over 40 Packages by kjok on Tuesday September 16, 2025 @12:35PM (#45264527)
Why should MS buy any of these startups when a developer (not any automated tech) found the malware? It looks like these startups did after-the-fact analysis for PR.
Re:Self Propagating NPM Malware Compromises over 40 Packages by singulasar on Wednesday September 17, 2025 @06:29AM (#45274026)
on the other hand, the previous supply chain attack was found by automated tech. Also, if MS would be so kind as to just run similar scans at the time a package is updated instead of after the package is updated (which is the only way the automated tech can run if npm doesn't integrate it), then malware like this would be way less common.

MS doesn't care

Re:Self Propagating NPM Malware Compromises over 40 Packages by kjok on Thursday September 18, 2025 @11:55AM (#45291220)
> on the other hand, the previous supply chain attack was found by automated tech.

Are you sure about this? Would love to see which ones.

Re:Self Propagating NPM Malware Compromises over 40 Packages by singulasar on Thursday September 18, 2025 @12:59PM (#45292071)
The chalk/debug one https://www.aikido.dev/blog/npm-debug-and-chalk-packages-com... I believe socket also found it this way just a bit later.

The dev later said that Charlie notifying him probably shaved off some very important time for the remediation.

So in this case 2 different companies found it using automated tech before anyone else

Re:Self Propagating NPM Malware Compromises over 40 Packages by CharlieEriksen on Friday September 19, 2025 @03:16AM (#45298801)
Hi, I'm Charlie from Aikido, as mentioned above. Yes, we detected it automatically, and I alerted Josh to the situation on BSky.

There's no reason why Microsoft/npm can't do what we're doing, or any of the other handful to dozen companies that do similar things to us, to protect the supply chain.