News for hackers. Stuff that matters.
Re:Concealed backdoor in fake AWS files escaped mainstream n... by belter on Thursday July 18, 2024 @08:16AM (#40994883)
And...it's NPM again....
Re:Concealed backdoor in fake AWS files escaped mainstream n... by lostmsu on Thursday July 18, 2024 @09:29PM (#41001355)
I am not a fan of JS ecosystem, but why do you think this issue is not mostly a function of popularity?
Re:Concealed backdoor in fake AWS files escaped mainstream n... by marcelnita on Thursday July 18, 2024 @07:06AM (#40994458)
Wondering why all those console.log calls ended up in the presumably final version of the exploit. All the more chances for someone to see what they were doing.
Re:Concealed backdoor in fake AWS files escaped mainstream n... by hfjke on Thursday July 18, 2024 @09:45AM (#40995542)
Wow, this is a pretty scary reminder of how easy it is to slip malicious code into widely used repositories. It’s crazy to think that something labeled as an AWS resource can go unnoticed for so long! Makes you wonder how many other similar backdoors are out there, quietly compromising dev environments. How can we better protect against these kinds of threats? Maybe it's time for some stricter vetting processes for open-source contributions?
Re:Concealed backdoor in fake AWS files escaped mainstream n... by salawat on Thursday July 18, 2024 @01:04PM (#40997620)
Or... Read code you depend for understanding before you use it. Then once you have something that works; lock it in. Repeat every update.

Suddenly backdoor threat will plummet, because every time some bastard violates the principle of least surprise, it sticks out like a sore thumb.

Code dependence, much like codependence, is harmful in excess.