News for hackers. Stuff that matters.
Re:NPM debug and chalk packages compromised by yifanl on Monday September 08, 2025 @02:47PM (#45172189)
Asking people to run random install scripts just feels very out of place given the context.
Re:NPM debug and chalk packages compromised by hunter2_ on Monday September 08, 2025 @03:28PM (#45172767)
I would agree if this were one of those `curl | sh` scenarios, but don't we consider things like `brew` to be sufficiently low-risk, akin to `apt`, `dnf`, and the like?
Re:NPM debug and chalk packages compromised by tripplyons on Monday September 08, 2025 @03:42PM (#45172964)
Anyone can upload an NPM package without much review. For Homebrew, you at least have to submit a pull request.
Re:NPM debug and chalk packages compromised by what on Monday September 08, 2025 @11:52PM (#45177196)
Homebrew has been compromised before. To think it’s immune is a bit naive.
Re:NPM debug and chalk packages compromised by n8m8 on Tuesday September 09, 2025 @10:14AM (#45182243)
Agreed that it's a bit funny given the context and no community-managed package manager should be 100% trusted.

That said, I think rg is pretty well known to linux daily-drivers and they just wanted to share something quickly for powerusers who want to check their workspaces quickly. Probably better to just instruct n00bs to use grep than install a whole cli tool for searching

Come to think of it, I wonder if a 2-phase attack could be planned by an attacker in the future: Inject malware into a package, flood guidance with instructions to install another popular tool that you also recently compromised... lol

Re:NPM debug and chalk packages compromised by tripplyons on Tuesday September 09, 2025 @11:40AM (#45183548)
I'm not saying its immune. I'm saying that NPM doesn't have as many protections, making NPM an easier target.
Re:NPM debug and chalk packages compromised by n8m8 on Tuesday September 09, 2025 @10:19AM (#45182290)
https://docs.brew.sh/Acceptable-Casks#apps-that-bundle-malwa...

> Unfortunately, in the world of software there are bad actors that bundle malware with their apps. Even so, Homebrew Cask has long decided it will not be an active gatekeeper (macOS already has one) and users are expected to know about the software they are installing. This means we will not always remove casks that link to these apps, in part because there is no clear line between useful app, potentially unwanted program, and the different shades of malware—what is useful to one user may be seen as malicious by another.

---

So there might be pull requests, but Brew's official stance is that they do not actively moderate casks for malware. I guess there's something built into the MacOS packaging step that help mitigate the risk, but I don't know much about it outside playing w/ app development in XCode.

Re:NPM debug and chalk packages compromised by dmitrygr on Monday September 08, 2025 @05:07PM (#45174003)
> don't we consider things like `brew` to be sufficiently low-risk,

Like ... npm?

Re:NPM debug and chalk packages compromised by fn-mote on Monday September 08, 2025 @06:38PM (#45175021)
Nah…

Everybody knows npm is a gaping security issue waiting to happen. Repeatedly.

It’s convenient, so it’s popular.

Many people also don’t vendor their own dependencies, which would slow down the spread at the price of not being instantly up to date.

Re:NPM debug and chalk packages compromised by dabockster on Monday September 08, 2025 @08:11PM (#45175798)
> Many people also don’t vendor their own dependencies, which would slow down the spread at the price of not being instantly up to date.

npm sold it really hard that you could rely on them and not have to vendor dependencies yourself. If I suggested that a decade ago in Seattle, I would have gotten booed out of the room.

Re:NPM debug and chalk packages compromised by marcus_holmes on Monday September 08, 2025 @10:33PM (#45176729)
I have repeatedly been met with derision when pointing out what a gaping security nightmare the whole Open Source system is, especially npm and its ilk.

Yet here we are. And this is going to get massively worse, not better.

Re:NPM debug and chalk packages compromised by Intermernet on Tuesday September 09, 2025 @05:39AM (#45179724)
Nothing specific to open source is to blame in this instance. The author got phished. Open source software often has better code vetting and verification than closed source software. npm, however, does not.
Re:NPM debug and chalk packages compromised by albedoa on Tuesday September 09, 2025 @12:57AM (#45177580)
> Nah…

I mean, I believe you, but the person you are replying to obviously believes that they are similar. Could you explain the significant differences?

Re:NPM debug and chalk packages compromised by johnisgood on Tuesday September 09, 2025 @02:38PM (#45186549)
Convenient, as in the barrier to entry is way too low. I am pretty much against it.
Re:NPM debug and chalk packages compromised by hunter2_ on Monday September 08, 2025 @05:52PM (#45174514)
I thought getting code into brew is blocked by some vetting (potentially insufficient, which could be argued for all supply chains), whereas getting code into npm involves no vetting whatsoever.
Re:NPM debug and chalk packages compromised by n8m8 on Tuesday September 09, 2025 @10:17AM (#45182278)
Went and found the link: https://docs.brew.sh/Acceptable-Casks#apps-that-bundle-malwa...

> Unfortunately, in the world of software there are bad actors that bundle malware with their apps. Even so, Homebrew Cask has long decided it will not be an active gatekeeper (macOS already has one) and users are expected to know about the software they are installing. This means we will not always remove casks that link to these apps, in part because there is no clear line between useful app, potentially unwanted program, and the different shades of malware—what is useful to one user may be seen as malicious by another.

Re:NPM debug and chalk packages compromised by anthk on Monday September 08, 2025 @05:24PM (#45174196)
APT repos for Debian, Trisquel, Ubuntu... require far more checkings and bureaucracy.
Re:NPM debug and chalk packages compromised by socalgal2 on Monday September 08, 2025 @05:40PM (#45174375)
I'll bet they don't. There's way to much churn for it all to be checked
Re:NPM debug and chalk packages compromised by const_cast on Monday September 08, 2025 @07:36PM (#45175530)
Churn? On Debian?

It takes like 2 years to get up to date packages. This isn't NPM.

Re:NPM debug and chalk packages compromised by SchemaLoad on Monday September 08, 2025 @11:06PM (#45176926)
The xscreensaver dev managed to very easily slip a timebomb in to the debian repos. Wasn't obscured in any way, the repo maintainers just don't review the code. It would be physically impossible for them to review all the changes in all the programs.
Re:NPM debug and chalk packages compromised by justusthane on Monday September 08, 2025 @06:35PM (#45174994)
No, they are extremely well vetted. Have you ever heard of a supply chain attack involving Red Hat, Debian or Ubuntu repos?
Re:NPM debug and chalk packages compromised by jonquest on Monday September 08, 2025 @06:56PM (#45175191)
Yes, the XZ attack affected Fedora nightly and Debian testing and unstable. Yes, it got caught before it made it into a stable distribution (this time).

https://www.redhat.com/en/blog/understanding-red-hats-respon...

https://lists.debian.org/debian-security-announce/2024/msg00...

Re:NPM debug and chalk packages compromised by goodpoint on Tuesday September 09, 2025 @08:37AM (#45181120)
So the attack was successfully stopped and you complain about it?
Re:NPM debug and chalk packages compromised by jonquest on Tuesday September 09, 2025 @02:34PM (#45186470)
I’m not complaining, I’m pointing out facts. If the facts offend you, that’s your problem. Ignore them if you wish.
Re:NPM debug and chalk packages compromised by justusthane on Monday September 08, 2025 @06:32PM (#45174960)
ripgrep is quite well known. It’s not some obscure tool. Brew is a well-established package manager.

(I get that the same can be said for said for npm and the packages in question, but I don’t really see how the context of the thread matters in this case).