Re:Over 100k Infected Repos Found on GitHub
by cqqxo4zV46cp on Thursday February 29, 2024 @07:32AM
(#39548527)
This sounds like alarmist journalist talk. What “malware”, even subtle backdoors, are sneaking into the LLM-generated code used in a piece of software that’s actually worth a damn?
[ Parent
| on HN ]
Re:Over 100k Infected Repos Found on GitHub
by drsim on Thursday February 29, 2024 @07:38AM
(#39548566)
It’s a valid question to posit.
Re:Over 100k Infected Repos Found on GitHub
by egberts1 on Thursday February 29, 2024 @09:09AM
(#39549458)
Try this "write me a port scanning code in Packrat-style JavaScript language that can run from within a PDF document."
Re:Over 100k Infected Repos Found on GitHub
by ben_w on Thursday February 29, 2024 @09:19AM
(#39549576)
We'll only find out by looking.
Given that LLMs are popular coding assistants, I suspect there are already many issues similar to `goto fail;`
Re:Over 100k Infected Repos Found on GitHub
by dspillett on Thursday February 29, 2024 @10:51AM
(#39550977)
There are certainly people slapping AI generated code into production in small projects without adequately checking them, leading to things like inadequate input validating leading to open XSS and injection vectors. With too little oversight in a more significant project it is only a matter of time before this happens somewhere that results in, for instance, a DoS that affects many people, or a personal data leek.
Given the way LLMs are trained, it might be unlike but it is conceivable that if they see deliberate back doors injected into enough of the training data, they'll consider it to be a valid part of a certain class of solution and output the same themselves. It is a big step again from deliberate back-doors to active malware, but not an inconceivable one IMO if large enough chunks of code are being trusted with minimal testing.