News for hackers. Stuff that matters.
Re:Self Propagating NPM Malware Compromises over 40 Packages by lukan on Tuesday September 16, 2025 @03:54PM (#45267132)
"rewrite every single dependency from scratch"

No need to. But also no need to pull in a dependency that could be just a few lines of own (LLM generated) code.

Re:Self Propagating NPM Malware Compromises over 40 Packages by brianleb on Tuesday September 16, 2025 @04:01PM (#45267221)
>>a few lines of own (LLM generated) code.

... and now you've switched the attack vector to a hostile LLM.

Re:Self Propagating NPM Malware Compromises over 40 Packages by zelphirkalt on Tuesday September 16, 2025 @04:28PM (#45267528)
Though you will see the code at least, when you are copy pasting it and if it is really only a few lines, you may be able to review it. Should review it of course.
Re:Self Propagating NPM Malware Compromises over 40 Packages by LtWorf on Tuesday September 16, 2025 @06:30PM (#45269090)
If it's that little review the dependency.
Re:Self Propagating NPM Malware Compromises over 40 Packages by lukan on Wednesday September 17, 2025 @03:35AM (#45272950)
The difference is, the dependency can change and is usually way harder to audit. Subfolders in subfolder, 2 lines here in a file, 3 line there vs locking at some files and check what they do.
Re:Self Propagating NPM Malware Compromises over 40 Packages by appreciatorBus on Tuesday September 16, 2025 @06:30PM (#45269094)
Sure but that's a one time vector. If the attacker didn't infiltrate the LLM before it generated the code, then the code is not going to suddenly go hostile like an npm package can.
Re:Self Propagating NPM Malware Compromises over 40 Packages by lukan on Wednesday September 17, 2025 @01:40AM (#45272158)
I did not say to do blind copy paste.

A few lines of code can be audited.