Developer convicted for “kill switch” code activated upon his termination
Developer convicted for “kill switch” code activated upon his termination
arstechnica.com
Developer convicted for “kill switch” code activated upon his termination
109 comments
-
This kill switch, the DOJ said, appeared to have been created by Lu because it was named "IsDLEnabledinAD," which is an apparent abbreviation of "Is Davis Lu enabled in Active Directory."
Lu named these codes using the Japanese word for destruction, "Hakai," and the Chinese word for lethargy, "HunShui,"
Lu]’s "disappointed" in the jury's verdict and plans to appeal
No, this guy is cooked, there’s even evidence of him looking up how to hide processes and quickly delete files, absolutely no way an appeal would work out for him, I don’t think an “I got hacked” argument is going to work.
-
It would only work if he owned the code and the company stopped paying. There's lots of precedent for that.
-
Still probably not. The code also deleted files, deleted accounts, and created infinite loops which took down large chunks of the network and infrastructure.
You could take your code, but you can't take down the company.
-
Yeah he's screwed then.
-
-
-
I take it he hasn't heard about "hiding things in the open".
That would be, for example, using a constant of some near year in "end time" column meaning unfinished action.
Or just making some part that will inevitably have to be changed - "write-only", as in unreadable. Or making documentation of what he did bad enough in some necessary places that people would have to ask him.
So many variants, and such obvious stupidity.
-
That's an amazing point, actually
-
-
It's actually kind of worrisome that they have to guess it was his code based on the function/method name. Do these people not use version control? I guess not, they sure as hell don't do code reviews if this guy managed to get this code into production
-
- I assumed that the code was running on a machine that Lu controlled.
- Most companies I have worked at had code reviews, but it was on the honor system. I am supposed to get reviews for all the code I push to main, but there is nothing stopping me from checking in code that was not reviewed (or getting code reviewed and making a change before pushing it). My coworkers trust me to follow the process and allow me to break the rules in an emergency.
-
-
109 comments