News for hackers. Stuff that matters.
Re:What NPM should do to stop a new colors attack by WJW on Monday January 10, 2022 @01:19PM (#29879063)
Nobody is forcing them to rewrite it or anything. Github canceled his account because knowingly posting malicious software is against the TOS, and it is not difficult to argue that putting infinite loops in the startup code of all your users is malicious. He still has the code on his computer to do whatever he pleases with. The rest of the world is just looking at it askew and calculating the odds something like this is going to happen again and what they should do about it. If you are going to be a dick to your users you should not be surprised that they will refuse to use your software afterwards.

In a way, it is kinda sad that this behavior drives him away from the financial security he so seemed to crave. "Yes I just caused your dev team to do hotfixes during the weekend and cost you XYZ dollars in downtime, can I have a senior dev position now plz" is not a very convincing line when interviewing.

Re:What NPM should do to stop a new colors attack by okl on Monday January 10, 2022 @01:31PM (#29879246)
I agree that it was a dick move from his side. Fork his project, or use an older version. I am not convinced that him breaking his code is something that ought to be punished.

GitHub gets the right to close their hand while Marak doesn't.

Re:What NPM should do to stop a new colors attack by watwut on Monday January 10, 2022 @06:09PM (#29884343)
I see it more as attempt to protect against another similar action. Not so much to punish as in "teach him" or "get revenge".