←back to thread

1208 points jamesberthoty | 1 comments | | HN request time: 0.21s | source
Show context
cddotdotslash ◴[] No.45262019[source]
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

replies(6): >>45262042 #>>45262074 #>>45262368 #>>45262518 #>>45263064 #>>45263487 #
m4r71n ◴[] No.45262368[source]
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...
replies(1): >>45262594 #
progbits ◴[] No.45262594[source]
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.
replies(3): >>45262772 #>>45263297 #>>45264527 #
foobarbecue ◴[] No.45263297[source]
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.

replies(2): >>45264766 #>>45266148 #
1. chatmasta ◴[] No.45266148[source]
Whoever made the exploit probably doesn’t use windows.