News for hackers. Stuff that matters.
Re:Nx compromised: malware uses Claude code CLI to explore t... by dudeinjapan on Wednesday August 27, 2025 @09:02AM (#45039083)
Are you affected? Run the affected program. OK, now you are definitely affected.
Re:Nx compromised: malware uses Claude code CLI to explore t... by baxtr on Wednesday August 27, 2025 @11:47AM (#45041280)
It might be even better than that:

Create a blog post about a security issue. Post it on HN get upvotes. Find people who believe they might be affected. Let them run the affected program. Boom.

Re:Nx compromised: malware uses Claude code CLI to explore t... by ghurtado on Wednesday August 27, 2025 @12:24PM (#45041752)
Either I've grown old and bitter enough that I think this is likely the case, or this is just a rational take and most likely what happened.

I'm not sure which is worse.

Re:Nx compromised: malware uses Claude code CLI to explore t... by littlecranky67 on Wednesday August 27, 2025 @09:13AM (#45039230)
Says the malware is in a post-install script - that will not be called by nx, but i.e after an npm install
Re:Nx compromised: malware uses Claude code CLI to explore t... by reactordev on Wednesday August 27, 2025 @10:22AM (#45040135)
Consider anything pre or post attached to the package as tainting the package.
Re:Nx compromised: malware uses Claude code CLI to explore t... by SoftTalker on Wednesday August 27, 2025 @10:28AM (#45040219)
Consider your entire system tainted, nothing is trustworthy at this point. Wipe and rebuild from known good media.
Re:Nx compromised: malware uses Claude code CLI to explore t... by littlecranky67 on Wednesday August 27, 2025 @11:22AM (#45040954)
The malware is "luckily" written in javascript and such quite easy to analyse. No manipulation outside of .zshrc or .bashrc and a temp txt file.
Re:Nx compromised: malware uses Claude code CLI to explore t... by tsukikage on Wednesday August 27, 2025 @12:42PM (#45041971)
That's what the code you can see now does. It may or may not be the same as what ran.
Re:Nx compromised: malware uses Claude code CLI to explore t... by littlecranky67 on Wednesday August 27, 2025 @02:54PM (#45043530)
Nope, because the script was commited to upstream and you can review what ended in the package.

It seems a lot of general "wisdom" here is thrown by people who have not looked into this particular incident or are unfamiliar with js node dev in general.

Re:Nx compromised: malware uses Claude code CLI to explore t... by reactordev on Wednesday August 27, 2025 @04:35PM (#45044858)
Correct, luckily, but all it takes is one eval. So be diligent about checking. However, like you said, luckily it’s JavaScript and there’s a history online that you can see.

Be weary of binary wasms though, harder to analyze. In the end, because it was published and npm allows you to see the history, we can all see.

Still, from a security standpoint, anything within a “package” that is compromised, compromises the package. Don’t install it. Wait for the fix.

Re:Nx compromised: malware uses Claude code CLI to explore t... by tempaccount420 on Thursday August 28, 2025 @01:13AM (#45048628)
WASM should be easier to analyze since you can't look at what functions the WASM imports to do side-effects.
Re:Nx compromised: malware uses Claude code CLI to explore t... by dudeinjapan on Wednesday August 27, 2025 @11:26AM (#45041022)
Oh good. I guess running the actual program was too many steps.