Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
Crime Security

Dev Gets 4 Years For Creating Kill Switch On Ex-Employer's Systems (bleepingcomputer.com) 53

Davis Lu, a former Eaton Corporation developer, has been sentenced to four years in prison for sabotaging his ex-employer's Windows network with malware and a custom kill switch that locked out thousands of employees once his account was disabled. The attack caused significant operational disruption and financial losses, with Lu also attempting to cover his tracks by deleting data and researching privilege escalation techniques. BleepingComputer reports: After a corporate restructuring and subsequent demotion in 2018, the DOJ says that Lu retaliated by embedding malicious code throughout the company's Windows production environment. The malicious code included an infinite Java thread loop designed to overwhelm servers and crash production systems. Lu also created a kill switch named "IsDLEnabledinAD" ("Is Davis Lu enabled in Active Directory") that would automatically lock all users out of their accounts if his account was disabled in Active Directory. When his employment was terminated on September 9, 2019, and his account disabled, the kill switch activated, causing thousands of users to be locked out of their systems.

"The defendant breached his employer's trust by using his access and technical knowledge to sabotage company networks, wreaking havoc and causing hundreds of thousands of dollars in losses for a U.S. company," said Acting Assistant Attorney General Matthew R. Galeotti. When he was instructed to return his laptop, Lu reportedly deleted encrypted data from his device. Investigators later discovered search queries on the device researching how to elevate privileges, hide processes, and quickly delete files. Lu was found guilty earlier this year of intentionally causing damage to protected computers. After his four-year sentence, Lu will also serve three years of supervised release following his prison term.

Dev Gets 4 Years For Creating Kill Switch On Ex-Employer's Systems

Comments Filter:
  • by Kisai ( 213879 ) on Friday August 22, 2025 @06:28AM (#65607200)

    Dude should have made it so if his manager's account was disabled. It would have been obvious if it was checking for his account. Consider it a parting gift. /s

    In all seriousness, kill-switches should only be created for military systems to self-destruct the device so that hardware that falls into the hands of the enemy self-destructs rather than remains operable. It makes it impractical of course in case someone loses the device.

    Any other situation, kill switches aren't even necessary, if you're someone vital to the operational stability of the company, then the minute you're gone, your presence missing will be noticed as maintenance stops functioning.

    • Re:Careless (Score:4, Informative)

      by mysidia ( 191772 ) on Friday August 22, 2025 @06:36AM (#65607210)

      kill-switches should only be created for military systems to self-destruct the device

      They are actually commonly used in the software industry for the purpose of disabling systems ifn case the customer forgot to make a payment to renew their license. For example: Backup software license expired, so the next day all the scheduled backup jobs are failing. Also, the buttons to start a manual backup or initiate a restore are greyed out requiring you to contact the vendor and pay for more time on that program's copyright license.

    • > if his manager's account was disabled

      Oh the chaos that would ensue. :)

      Narcissists often get caught because they lack subtlety.

      • Maybe that is why your favorite abuser of underage girls and enabler of romance scammers is in jail for his financial crimes.
    • by taustin ( 171655 )

      Any other situation, kill switches aren't even necessary, if you're someone vital to the operational stability of the company, then the minute you're gone, your presence missing will be noticed as maintenance stops functioning.

      The world is full of people who see themselves as vital, who actually aren't. This is how they cope with that reality.

      • by v1 ( 525388 )

        People that consider themselves vital, but then have to take steps to create artificial vitality - their own actions are proving them wrong.

        If you were truly vital, your simple absence would be a disaster all by itself. If you have to engineer that condition, you're NOT vital. This is just an arrogant, self-important narcissist behaving badly and getting what they've got coming, at the cost of others.

        I don't think there are enough stories like this in the news. It's pretty easy to find accounts BY such i

      • The world is full of people who see themselves as vital, who actually aren't. This is how they cope with that reality.

        In a large company, if there is someone who is truly vital, then management at that company has failed. It's the bus test: "what would happen if xzy fell under a bus tomorrow?".

        While no-one is truly irreplaceable, the issue is cost and time. In a small company, the cost and time to replace some employees may be fatal to the company.

  • Fool (Score:5, Funny)

    by dwywit ( 1109409 ) on Friday August 22, 2025 @06:32AM (#65607204)

    "how to elevate privileges, hide processes, and quickly delete files"

    He had to look that up? What an incompetent fool. He deserves his sentence.

    Makes the rest of us look bad.

    • by Viol8 ( 599362 )

      I'm not sure hiding processes would be considered basic knowledge.

    • Re:Fool (Score:4, Funny)

      by AmiMoJo ( 196126 ) on Friday August 22, 2025 @06:46AM (#65607216) Homepage Journal

      Does sound like amateur hour. After I left the company contracted me to fix a few things because they didn't hire a replacement in time and the guy they got couldn't wrap his head around the systems I had built. Didn't even have to try to sabotage anything, and it was all well documented. All you really need to do is rely on the company to screw it up themselves.

    • Re:Fool (Score:5, Insightful)

      by gweihir ( 88907 ) on Friday August 22, 2025 @07:11AM (#65607280)

      It is not surprising he had to look this up. A competent IT security person would not have done it, because it is exceptionally likely that you will get caught. It is always the amateurs with delusions that do this crap.

      • by madbrain ( 11432 )

        Imagine for a moment if the company wasn't competent enough to trace it back to him.
        They would then have no idea that the damage happened as a result of his firing.

        Can you really enjoy your revenge, if the victim doesn't even know that it was revenge ?
        I think it is a bit of a conundrum. It might be why he didn't even try to hide it.

        • by gweihir ( 88907 )

          Good point. Angry, aggressive, out for revenge and not thinking about the consequences for himself at all. Essentially an intellectual child.

  • ...that the company already realised that the guy was a bit of a jackjass. A demotion is a clear message that "we think you're a waste of desk space but you're not so useless that we can fire you but perhaps you should think about looking elsewhere"

    • by DarkOx ( 621550 )

      Generally but not always. I used to work with a guy who got promoted to director. He wasn't terribly good at it. It was a shift lower management that he was very good at. However it also represented the change from tactical problem solving to strategic thinking and to pitching ideas and convincing people you mostly report to ie VPs, and C-Suite, vs organizing people who mostly report to you.

      It was perfectly clear to everyone, including him after 8 months or so he was just not working out in the new role

      • by Viol8 ( 599362 )

        I've always avoided moving into management despite having had the oipportunity a few times. I'm not a people person, I'm not interested in managing them or dealing with their issues, I'm far better doing stuff on a computer. Probably cost me a fair amount of money in the long run but I've no regrets.

  • Sigh (Score:4, Insightful)

    by ledow ( 319597 ) on Friday August 22, 2025 @07:22AM (#65607314) Homepage

    Tell me why a dev has access to AD enough to lock out other people, including admins.

    This is just dumb-ass network management.

    • by DarkOx ( 621550 )

      I would guess it is pretty common in large enterprises. Most of them will have some custom identity and access management solutions, even if it just glue to make some actions in PeopleSoft/SAP/Pick-your-HR-IS-SaaS-thing trigger events in AD:DS/Entra/Okta/AWS-IAM/etc.

      Maybe they don't have an account themselves with access but if they commit some code that gets promoted to production and runs with account privileges that do...well bob's your uncle.

    • by MeNeXT ( 200840 )

      Because the PHB thinks it's a good idea.

      Security is important until the president is shown a presentation of this cool new gizmo/fad.

    • Tell me why a dev has access to AD enough to lock out other people, including admins.

      Perhaps it is because Windows has frequent security issues?

  • Shows he either really likes his initials, or did not care if he got caught, or both.

    In the good old days, he could have used self-modifying code to try to cover his tracks a little bit.

    • Shows he either really likes his initials, or did not care if he got caught, or both.

      You could call it WatermelonRutabaga and the test would still have to point to the account in order to function, so it would still be self-documenting.

  • That guy just made sure he will never be hired again for the same or similar functions again.

    • It’s a youthful mistake. Won’t the 4 years spent in prison be enough for him to deserve a second chance?
      • by taustin ( 171655 )

        No. People that full of themselves (and malice) do not learn. I wouldn't hire someone with that poor of judgement, and that delusional a view of their own abilities, to flip burgers.

  • So no one does code reviews anymore? No one noticed new code going into a codebase?
    • Yeah, lots of red flags all over the place. If one person can create a disaster like this, what else is this company doing horribly wrong? I wouldn't trust them with my information, that's for sure.

    • by sloth jr ( 88200 )
      Why would you follow code review policy when you're writing and installing malware? Are you expecting a Change Management meeting? Guy wrote a program and installed it, not like it was part of production code base.

      Now, why he had access to AD, that's a different and very interesting question that does raise the same sort of question you're alluding to.
    • Would he commit to a repo? Why? Such a system would be deployed without due process

Everybody likes a kidder, but nobody lends him money. -- Arthur Miller

Working...