Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Malicious versions of Nx and some supporting plugins were published

github.com

Post reply on HN
Print view View original

21–30 of 460 posts

Re: Malicious versions of Nx and some supporting plugins were published

#21

Post by fooqux »

echelon wrote: post #7
algo_lover wrote: post #5

aaaand it begins! > Interestingly, the malware checks for the presence of Claude Code CLI or Gemini CLI on the system to offload much of the fingerprintable code to a prompt. > The packages in npm do not appear to be in Github Releases > First Compromised Package published at 2025-08-26T22:32:25.482Z > At this time, we believe an npm token was compromised which had publish rights to the affected packages. > The compr…

Wild to see this! This is crazy. Hopefully the LLM vendors issue security statements shortly. If they don't, that'll be pretty damning. This ought to be a SEV0 over at Google and Anthropic.

> Hopefully the LLM vendors issue security statements shortly. If they don't, that'll be pretty damning.

Why would it be damning? Their products are no more culpable than Git or the filesystem. It's a piece of software installed on the computer whose job is to do what it's told to do. I wouldn't expect it to know that this particular prompt is malicious.

Re: Malicious versions of Nx and some supporting plugins were published

#22

Post by [deleted] »

echelon wrote: post #19

Google and Anthropic: this is a SEV0. Assemble your teams and immediately do the following: 1. Issue a public statement that you are aware of this issue and are tracking it 2. Begin monitoring your analytics to see which customers are impacted and shut down their access 3. Reach out to impacted customers and let them know you'll be preparing a list of next steps for them. 4. Monitor for a wider blast radius or larger…

[deleted]

Re: Malicious versions of Nx and some supporting plugins were published

#23

Post by echelon »

fooqux wrote: post #21
echelon wrote: post #7

Earlier quoted context omitted.

Wild to see this! This is crazy. Hopefully the LLM vendors issue security statements shortly. If they don't, that'll be pretty damning. This ought to be a SEV0 over at Google and Anthropic.

> Hopefully the LLM vendors issue security statements shortly. If they don't, that'll be pretty damning. Why would it be damning? Their products are no more culpable than Git or the filesystem. It's a piece of software installed on the computer whose job is to do what it's told to do. I wouldn't expect it to know that this particular prompt is malicious.

Then safety and alignment are a farce and these are not serious tools.

This is 100% within the responsibility of the LLM vendors.

Beyond the LLM, there is a ton of engineering work that can be put in place to detect this, monitor it, escalate, alert impacted parties, and thwart it. This is literally the impetus for funding an entire team or org within both of these companies to do this work.

Cloud LLMs are not interpreters. They are network connected and can be monitored in real time.

Re: Malicious versions of Nx and some supporting plugins were published

#24

Post by yuyu789 »

echelon wrote: post #19

Google and Anthropic: this is a SEV0. Assemble your teams and immediately do the following: 1. Issue a public statement that you are aware of this issue and are tracking it 2. Begin monitoring your analytics to see which customers are impacted and shut down their access 3. Reach out to impacted customers and let them know you'll be preparing a list of next steps for them. 4. Monitor for a wider blast radius or larger…

[dead]

Re: Malicious versions of Nx and some supporting plugins were published

#25

Post by croes »

f311a wrote: post #11

People really need to start thinking twice when adding a new dependency. So many supply chain attacks this year. This week, I needed to add a progress bar with 8 stats counters to my Go project. I looked at the libraries, and they all had 3000+ lines of code. I asked LLM to write me a simple progress report tracking UI, and it was less than 150 lines. It works as expected, no dependencies needed. It's extremely simpl…

Without these dependencies there would be no training data so the AI can write your code

Re: Malicious versions of Nx and some supporting plugins were published

#27

Post by octo888 »

echelon wrote: post #19

Google and Anthropic: this is a SEV0. Assemble your teams and immediately do the following: 1. Issue a public statement that you are aware of this issue and are tracking it 2. Begin monitoring your analytics to see which customers are impacted and shut down their access 3. Reach out to impacted customers and let them know you'll be preparing a list of next steps for them. 4. Monitor for a wider blast radius or larger…

A single top-level comment would suffice. No need to reply to various comments with the same kind of message

Re: Malicious versions of Nx and some supporting plugins were published

#28

Post by fsflover »

roenxi wrote: post #4

Honest to goodness, I do most of my coding in a VM now. I don't see how the security profile of these things are tolerable. The level of potential hostility from agents as a malware vector is really off the charts. We're entering an era where they can scan for opportunities worth >$1,000 in hostaged data, crypto keys, passwords, blackmail material or financial records without even knowing what they're looking for whe…

> I do most of my coding in a VM now

Perhaps you may be interested in Qubes OS, where you do everything in VMs with a nice UX. My daily driver, can't recommend it enough.

Re: Malicious versions of Nx and some supporting plugins were published

#29

Post by dpoloncsak »

echelon wrote: post #19

Google and Anthropic: this is a SEV0. Assemble your teams and immediately do the following: 1. Issue a public statement that you are aware of this issue and are tracking it 2. Begin monitoring your analytics to see which customers are impacted and shut down their access 3. Reach out to impacted customers and let them know you'll be preparing a list of next steps for them. 4. Monitor for a wider blast radius or larger…

What does Google or Antropic have to do with anything here? NX was compromised. Threat actors are using this access to leverage CLI LLMs to search the computer for you. Is this any different than if they just ran a big /find?

Should the AI Assistant NOT reply to the request it was given? Why shouldn't it?

Re: Malicious versions of Nx and some supporting plugins were published

#30

Post by lionkor »

echelon wrote: post #23
fooqux wrote: post #21

Earlier quoted context omitted.

> Hopefully the LLM vendors issue security statements shortly. If they don't, that'll be pretty damning. Why would it be damning? Their products are no more culpable than Git or the filesystem. It's a piece of software installed on the computer whose job is to do what it's told to do. I wouldn't expect it to know that this particular prompt is malicious.

Then safety and alignment are a farce and these are not serious tools. This is 100% within the responsibility of the LLM vendors. Beyond the LLM, there is a ton of engineering work that can be put in place to detect this, monitor it, escalate, alert impacted parties, and thwart it. This is literally the impetus for funding an entire team or org within both of these companies to do this work. Cloud LLMs are not interp…

You mean the safety and alignment that boils down to telling the AI to "please not do anything bad REALLY PLEASE DONT"? lol working great is it
Post reply on HN