Up to 10 years is crazy. Sure, what he did was wrong, planned and malicious, and they claim it cost them tens of thousands of dollars. But 10 years? This is crazy for something that at worst would be a yearly salary of a single employee.
Fucking capitalism.
he should have tried to overthrow the government, or stole classified documents. that’s a drastically lower sentence
allegedly costing hundreds of thousands of dollars in losses.
Also it’s sabotage, which might attract heavier penalties than mere theft?
Actually for federal sentencing, property destruction is punished under the same table as theft. It’s mostly measured from the amount of loss to the victims, whether the person actually profited from it or not.
Fair enough.
Having known victims of vandalism I can say it hurts more than theft.
Removed by mod
Now to make it worse, ask this, “If the corporation did 10 times this amount of damage, but to the general citizens of the country, how many people would go to jail?”
That’s right 0 people would go to jail! And they would only be fined for no more than 10% of the profit they made while doing it. Maybe someone like a jr director of operations gets tossed in jail, but he wasnt really apart of the club.
Nah they would have added more fees to subsidize the protections they weren’t going to put in place. Then reach out to the government for subsidies to put these protections in place. Then give bonuses, stock buy backs and when it happened again, they’d raise the fees installed previously and consider making the upgrades if the fine threatened is high enough, if not they’ll pay the fine and buy back more stock and run an ad campaign to make the company look better.
“Up to 10 years” is the maximum possible for that type of crime. Actual sentencing guidelines for a $500k loss for a first time offender will probably come out to about 2, maybe 3 years.
In order for the recommended sentence to hit 10 years, we’d have to be talking about damage of over $550 million, or something like a long criminal history.
Substantial disruption of critical infrastructure would get someone to around 5 years, as a reference.
deleted by creator
Don’t F with the power grid.
owned by the Ohio- and Dublin-based power management company Eaton Corp.
https://en.m.wikipedia.org/wiki/Eaton_Corporation
Sentences are always harsh for anything to do with those who provide for public utilities.
@null_dot@lemmy.dbzer0.com has a comment about sabotage, which was likely a factor combined with this to drive max recommended sentencing.
That’s hilarious.
A 55-year-old software developer
… and…
Lu had worked at Eaton Corp. for about 11 years when he apparently became disgruntled by a corporate “realignment” in 2018 that “reduced his responsibilities,” the DOJ said.
So he was 48 at the time he started this. Was he planning on retiring from all work at 48? I can’t imagine any other employer would want to touch him with a 10ft (3.048 meters) pole after he actively sabotaged his prior employer’s codebase causing global outages.
I’m sure DOGE is actively considering hiring him.
Koala tea internal code review practices
He fucked up. But it’s also kinda funny.
And now imagine doing this or sort of this destruction in a smaller company that has one to three mediocre admins at highest. One can kill this company and they would never get it why the computers got weird.
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.
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.
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.
We’ve all considered it
Oh yeah, but the thing that usually offsets the intrusive thoughts is a lot of courts treat this as the crime of “hurting rich people” which comes with like 30 years in pound you in the ass penitentiary.
Oh. Personally for me it’s code reviews that prevent me from doing it, but pound you in the ass penitentiary is a good motivation too
The secret is get promoted to where you do the code reviews. Then just get too busy to do them reliably. Timebomb activated.
Initially makes me wonder how the employer could be so dumb as to give one employee so much access. But then I remember a former employer of mine did the same and worse.
Colleague was known for writing his comments in such a way that only he could read them, including mixing in German (US based company doing all business in English). He was also the admin of our CAD system and would use it as leverage to get his way on things, including not giving even default user access to engineers he didn’t like. We migrated systems and everyone was thinking, “this is it, the chance to root this guy out of the admin position” and… they gave him admin access again. Not even our IT department had the access he had. I left before the guy retired / was fired, this post is making me wonder if he left peacefully or left bricking the CAD system out.
Initially makes me wonder how the employer could be so dumb as to give one employee so much access.
Right now, just based purely on the access I need to do my day-to-day job involves me having access where I can pretty much nuke everything from orbit, with an ssh loop.
At some point, you need to trust your employees, in order to get work done. Sure, you can lock it all down tightly, but then you just made work take longer. It’s a trade off.
Initially makes me wonder how the employer could be so dumb as to give one employee so much access.
The amount of access he had doesn’t surprise me. He’d been there for 11 years already likely working on many things as he interacted with systems in the course of his legitimate work. While its possible to set up access and permissions in an organization utilizing the “least privilege principle”, its expensive, difficult to maintain, and adds lots of slowdowns in velocity to business operations. Its worth it to prevent this exact case from the article, but lots of companies don’t have the patience or can’t afford it.
My previous work didn’t revoked my access to their CMS. I was so upset when they laid me off after telling them my wife is pregnant.
But I ain’t that stupid.
Aren’t you no longer binded by profesional silence? Just log in into their DB, export it and try to get a seller
Again, not that stupid.
Why do kill switches when you can just hog all the work of maintaining some critical part of the infrastructure and make it’s functioning and maintenance so opaque and impenetrable that the employer can’t replace or fire you without their shit catching fire soon after. It doesn’t have to be malicious or illegal.
His efforts to sabotage their network began that year, and by the next year, he had planted different forms of malicious code, creating “infinite loops” that deleted coworker profile files, preventing legitimate logins and causing system crashes
I wish this guy was were actually politically motivated, but he seems to have been just really petty minded person.
so opaque and impenetrable that the employer can’t replace or fire you without their shit catching fire soon after.
Somehow, that’s the kinda roles I always land in lol
Why do kill switches when you can just hog all the work of maintaining some critical part of the infrastructure and make it’s functioning and maintenance so opaque and impenetrable that the employer can’t replace or fire you without their shit catching fire soon after.
This is literally my firm’s core business practice. We’ve been at it for so long that at this point we have to be included in competing bids because we are the only ones in the world that can do certain specific things.
That’s what my old company used to do. You did this? Do a KT to some underpaid remote employee and when they leave it’s again your responsibility to maintain it, alongside the new bugs and spaghetti they introduced.
We once told a SP50 customer that we would not provide a business critical service because an employee went on sabatical for a month and she had the only working version on her cookery computer. At that point the customer was so integrated with us that it would take them years to replace us.
Reminds me of the timebombs in windows 2000. I guess he’s forced to start fresh.
Timebombs in Windows 2000?
Timebombs in windows 2000!
Oh shit that is a large number
out of the loop :
2000 x 1999 x 1998 x … x 3 x2 x 1 = 2000 !
guy really tagged his name on the kill function, which was running on his own system. smh my head
I worked for a company once that installed a remote-activation killswitch in their drivers, as a secret weapon to force the customer to stay current on their maintenance contract.
The CEO was a fuckup however, and the code killed their system even without being activated - resulting in a bunch of angry phonecalls and some of the most egregious lying I’ve ever heard.
god, he was a piece of shit
Sounds like lawsuit territory
So when company do it it’s fine but when we do it to companies it’s not?
Literally the same day as the HP news.
what happened?
(updated with a link)
Naturally. Advantage, privilege and money should only be in the hands of those who run large companies or better.
If that made you angry, bear in mind that’s what most top level company executives think. Well, actually they don’t think it, they know it unconsciously as the true order of the universe they inhabit and they get really uncomfortable should it even look vaguely like someone might be trying a competing philosophy to their own.
To be fair though, most people get really uncomfortable when something might undermine even part of the philosophy they live by.
Lol everyone probably fantasizes about such thing sometimes, but even if you weren’t caught, it’s not worth it to personally be bitter like that.
Just got laid off and could had done the same. Except I don’t have to. Internal systems are so bad and undocumented and I was like only IT specialist there who could use linux, and so many things related to core businesses were just basically behind me.
The kill switch has made it self. Funny how I would have written more documentation if I ever was given the time.
Same for my last job. My bosses and managers harassed and insulted me. They said I was useless and stupid.
I quit with 3 months of “notice” (standard in France to help you find a new job). They didn’t care during those 3 months. In the last week they panicked because they could not find a replacement that did everything I fixed every day.
I also interviewed my replacement, a junior out of school with big diplomas. When I asked if he knew Linux, he said “not really.” I thought “they are fucked with this guy.” They wanted to hire him because he was the son of some guy. I said to my boss that he would be a perfect fit for the company.
Unknowingly I was the kill switch. I sent them one last email with all the information they needed and told them to go fuck themselves in a polite way.
malicious compliance, I like it
but even if you weren’t caught, it’s not worth it to personally be bitter like that.
Really depends on what you do for a living… Non-profit? Sure. Weapons manufacturer? Fucking have at it.
Fair but I wouldn’t ever work for weapons manufacturing. Also sabotage in that context would have heavy punishment, and at worst could cause collateral damage.
I was using that as an example because it was the worst thing that came to mind. There is a whole gradient between non-profit and weapons manufacturer.
But don’t be stupid about it. Stash a date somewhere that you manually update every so often (so that it’ll stop being updated if you’re fired) and then add a bunch of random waits whose durations scale with the time since that date. If you’re worried that the code will be found, comment it with some bullshit about avoiding race conditions.
…and now I can’t use that idea, since this comment would be used in court. If I did it to a weapons manufacturer, they’d probably get the death penalty somehow.
comment it with some bullshit about avoiding race conditions
Lmao, amazing
I didn’t plant anything and I could still brick the production backends of a former employer because some poor ass decisions were made when choosing technologies and then when I pointed it out that it’s pretty bad the technology was stuck with so literally all it takes is sending 2-3 requests so all pods die.
But why do it.
Similar cases with my old company. In my case people who would had suffered the most direct consequences would had been my colleagues who I respect.
But I could totally cause trouble without any backdoor access.
