this post was submitted on 01 Jun 2026
86 points (97.8% liked)

Cybersecurity

10375 readers
209 users here now

c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.

THE RULES

Instance Rules

Community Rules

If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.

Learn about hacking

Hack the Box

Try Hack Me

Pico Capture the flag

Other security-related communities !databreaches@lemmy.zip !netsec@lemmy.world !securitynews@infosec.pub !cybersecurity@infosec.pub !pulse_of_truth@infosec.pub

Notable mention to !cybersecuritymemes@lemmy.world

founded 3 years ago
MODERATORS
top 19 comments
sorted by: hot top controversial new old
[–] davidgro@lemmy.world 42 points 2 months ago (3 children)

I'm beginning to think this "NPM" thing isn't a great idea.

[–] ztwhixsemhwldvka@lemmy.world 20 points 2 months ago

Its always npm

[–] NotSteve_@lemmy.ca 6 points 2 months ago (2 children)

I don't really see how it's NPM at fault here. This was caused by a malicious actor taking control of an account and putting out bad packages on it. It could happen on any package repository for any language

[–] davidgro@lemmy.world 6 points 2 months ago (1 children)

My understanding is that for most package managers the signing keys are held by a smallish number of maintainers responsible for entire sections, who presumably keep those accounts pretty tightly secured. Not impossible to take over, but it's a smaller attack surface.

While for NPM as far as I know every uploader keeps their own account and there's not even signing keys to lose control of.

[–] hirihit640@sh.itjust.works 4 points 2 months ago

I've heard quite a few PyPi and Cargo attacks though, but I bet the main reason why hear NPM so much is simply because NPM is the biggest, and thus the most valuable target

[–] MonkderVierte@lemmy.zip 3 points 2 months ago

Trust by default for a atomic packaging system. Entirely NPM's fault.

[–] Fizz@lemmy.nz 4 points 2 months ago (2 children)

I'm not familiar with npm but why is this always NPM? Is it a specific issue they have?

[–] knobbysideup@sh.itjust.works 24 points 2 months ago (1 children)

It's a "package manager" that has zero integrity checks built in. Web devs also love it. Nice combination.

[–] MonkderVierte@lemmy.zip 2 points 2 months ago

Culture problem imo.

[–] hirihit640@sh.itjust.works 0 points 2 months ago

because it's the biggest. Just like how hackers target windows and not linux (assuming they are targeting users and not servers).

[–] homes@piefed.world 11 points 2 months ago* (last edited 2 months ago)

One day, back in 1995, I could download every red hat package onto a series of 13 floppies.

In fact, it was required if you wanted to install red hat. So was compiling them all onto your own computer.

How far we’ve come

[–] atzanteol@sh.itjust.works 1 points 2 months ago
[–] certified_expert@lemmy.world 1 points 2 months ago

What was the red hat meaning?