News for hackers. Stuff that matters.
Re:Self Propagating NPM Malware Compromises over 40 Packages by shakna on Tuesday September 16, 2025 @05:18PM (#45268191)
Requiring you to audit both security and robustness on the LLM generated code.

Creating two problems, where there was one.

Re:Self Propagating NPM Malware Compromises over 40 Packages by bennyg on Tuesday September 16, 2025 @07:54PM (#45269859)
I didn't say generate :) - in all seriousness, I think you could reasonably have it copy the code for e.g. lodash.merge() and paste it into your codebase without the headaches you're describing. IMO, this method would be practical for a majority of npm deps in prod code. There are some I'd want to rely on the lib (and its maintenance over time), but also... a sort function is a sort function.
Re:Self Propagating NPM Malware Compromises over 40 Packages by shakna on Tuesday September 16, 2025 @08:44PM (#45270170)
LLMs don't copy and paste. They ingest and generate. The output will always be a generated something.
Re:Self Propagating NPM Malware Compromises over 40 Packages by TheBicPen on Tuesday September 16, 2025 @10:04PM (#45270709)
In 2022, sure. But not today. Even something as simple as generating and running a `git clone && cp xyz` command will create code not directly generated by the LLM.
Re:Self Propagating NPM Malware Compromises over 40 Packages by boomlinde on Thursday September 18, 2025 @06:56AM (#45288106)
In what way do you think this rebuts the message you responded to?
Re:Self Propagating NPM Malware Compromises over 40 Packages by lgas on Wednesday September 17, 2025 @05:44PM (#45281752)
You can give an LLM access to tools that it can invoke to actually copy and paste.
Re:Self Propagating NPM Malware Compromises over 40 Packages by vFunct on Tuesday September 16, 2025 @10:55PM (#45271077)
LLMs can do the audits now.