Remix.run Logo
jamesberthoty 5 hours ago

A lot of blogs on this are AI generated and such as this is developing, so just linking to a bunch of resources out there:

Aikido - https://www.aikido.dev/blog/s1ngularity-nx-attackers-strike-...

Socket - https://socket.dev/blog/ongoing-supply-chain-attack-targets-...

Ox - https://www.ox.security/blog/npm-2-0-hack-40-npm-packages-hi...

Safety - https://www.getsafety.com/blog-posts/shai-hulud-npm-attack

Phoenix - https://phoenix.security/npm-tinycolor-compromise/

Semgrep - https://semgrep.dev/blog/2025/security-advisory-npm-packages...

cddotdotslash 4 hours ago | parent | next [-]

I wonder who actually discovered this attack? Can we credit them? The phrasing in these posts is interesting, with some taking direct credit and others just acknowledging the incident.

Aikido says: > We were alerted to a large-scale attack against npm...

Socket says: > Socket.dev found compromised various CrowdStrike npm packages...

Ox says: > Attackers slipped malicious code into new releases...

Safety says: > The Safety research team has identified an attack on the NPM ecosystem...

Phoenix says: > Another supply chain and NPM maintainer compromised...

Semgrep says: > We are aware of a number of compromised npm packages

advocatemack 3 hours ago | parent | next [-]

Mackenzie here I work for Aikido. This is a classic example of the security community all playing a part. The very first notice of this was from a developer named Daniel Pereira. He alerted Socket who did the first review of the Malware and discovered 40 packages. After, Aikido discovered an additional 147 packages and the Crowdstrike packages. I'm not sure how Step found it but they were the first to really understand the malware and that it was a self replicating worm. So multiple parties all playing a part kinda independent. Its pretty cool

jamesberthoty 4 hours ago | parent | prev | next [-]

Several individual developers seem to have noticed it at around the same time with Step and Socket pointing to different people in their blogs.

And then vendors from Socket, Aikido, and Step all seem to have detected it via their upstream malware detection feeds - Socket and Aikido do AI code analysis, and Step does eBPF monitoring of build pipelines. I think this was widespread enough it was noticed by several people.

m4r71n 4 hours ago | parent | prev | next [-]

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...

progbits 3 hours ago | parent [-]

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.

codazoda 3 hours ago | parent | next [-]

Somehow I didn't realize GitHub purchased npm in 2020. GitHub is the second word on npmjs.org. How did I not notice?

octo888 2 hours ago | parent [-]

Microsoft: GitHub, NPM, typescript, VS Code, OpenAI, Playwright

A lot of fingers in a lot pies

kjok an hour ago | parent | prev | next [-]

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.

foobarbecue 3 hours ago | parent | prev [-]

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.

acomjean an hour ago | parent [-]

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.

augzodia 4 hours ago | parent | prev | next [-]

OP article says: > The incident was discovered by @franky47, who promptly notified the community through a GitHub issue.

codazoda 3 hours ago | parent [-]

Points to this, which does look like the first mention.

https://github.com/scttcper/tinycolor/issues/256

3 hours ago | parent | prev | next [-]
[deleted]
Onavo 2 hours ago | parent | prev [-]

Usually security companies monitor CVEs and the security mailing lists. That's how they all end up releasing the blog posts at the same time. It's because they are all using the same primary source.

redbell 4 hours ago | parent | prev | next [-]

Related (7 days ago):

NPM debug and chalk packages compromised (1366 points, 754 comments): https://news.ycombinator.com/item?id=45169657

flanbiscuit 2 hours ago | parent | next [-]

Related in that this is another, separate, attack on npm.

No direct relation to the specific attack on debug/chalk/error-ex/etc that happened 7 days ago.

The article states that this is the same attackers that got control of the "nx" packages on August 27th, which didn't really get a lot of traction on HN when it happened: https://hn.algolia.com/?dateRange=pastMonth&page=0&prefix=fa...

xrisk 4 hours ago | parent | prev [-]

Seems to be a separate incident?

nine_k 4 hours ago | parent [-]

Separate? Yes. Unrelated? Hard to tell.

junon an hour ago | parent [-]

It's unrelated in every observable technical way, but related in that it's a bit crazy how often this is happening to npm lately.

I'm glad it wasn't this particular attack that hit me last week.

liveoneggs 4 hours ago | parent | prev [-]

I guess it's still spreading? those blogs seem to list differences packages