News for hackers. Stuff that matters.
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.