News for hackers. Stuff that matters.
Re:Developer sabotaged ex-employer with kill switch that act... by jarsin on Friday March 07, 2025 @09:21PM (#43296956)
I never understand these types that are smart enough to crash an entire company, but too stupid to make it look like someone else did it.
Re:Developer sabotaged ex-employer with kill switch that act... by jmugan on Friday March 07, 2025 @09:49PM (#43297069)
I thought you were going to say "smart enough to crash an entire company, but too stupid to realize that their intelligence should be put to other uses."
Re:Developer sabotaged ex-employer with kill switch that act... by progbits on Friday March 07, 2025 @09:28PM (#43296983)
Could be the case here :)

"You only hear about the ones that get caught"

Re:Developer sabotaged ex-employer with kill switch that act... by jarsin on Friday March 07, 2025 @09:36PM (#43297017)
He literally wrote a script that locked out everyone on the network the second they disabled his employee account in active directory. He even named the variable Is[DH]EnabledInAD where [DH] is his initials.
Re:Developer sabotaged ex-employer with kill switch that act... by toast0 on Friday March 07, 2025 @09:44PM (#43297052)
Well the script is there, but maybe someone else put it there, because they were leaving/being forced out and they wanted to sabotage the company and make it look bad for DH (Article says DL).

No need to sabotage the company immediately, revenge is a dish best served cold.

Re:Developer sabotaged ex-employer with kill switch that act... by theamk on Friday March 07, 2025 @10:45PM (#43297314)
Unlikely, given that he confessed and that in other attack, he damaged the machine only he had access to.

I mean, it is theoretically possible there were two disgruntled employees, and second one pinned his crimes to the first one, but I think this is pretty unlikely, given the observeed lack of common sense.

Re:Developer sabotaged ex-employer with kill switch that act... by droopyEyelids on Friday March 07, 2025 @10:36PM (#43297276)
It could even have been another employee putting the idea into his head and encouraging him.
Re:Developer sabotaged ex-employer with kill switch that act... by theamk on Friday March 07, 2025 @10:46PM (#43297317)
Other employee, reddit story, AI chatbot, crime show... it does not matter who put the idea in the head, all that matters is who did the deed.
Re:Developer sabotaged ex-employer with kill switch that act... by droopyEyelids on Tuesday March 11, 2025 @01:14PM (#43334759)
Matters to whom
Re:Developer sabotaged ex-employer with kill switch that act... by naruhodo on Friday March 07, 2025 @10:13PM (#43297164)
My reaction too. It reminds me of the Simpsons' "Buttzilla" bit.

https://www.youtube.com/watch?v=DPmeLibaVwg&t=112s

Re:Developer sabotaged ex-employer with kill switch that act... by cozzyd on Friday March 07, 2025 @10:00PM (#43297112)
Must have messed up a decimal or some other mundane detail
Re:Developer sabotaged ex-employer with kill switch that act... by dietr1ch on Friday March 07, 2025 @10:00PM (#43297111)
A problem is that they can hire smart people to run the investigation, so the target on who to fool moves abruptly.
Re:Developer sabotaged ex-employer with kill switch that act... by ChrisMarshallNY on Friday March 07, 2025 @09:30PM (#43296989)
There have always been people like this, that are simply brainsick and petty, but it's something that is probably being exacerbated by the extreme animosity between the people that run companies, and the people that work on the front lines.

I'm not naive enough to think there was a "golden age," when everyone was happy-dappy, but I think it's much worse, now, than it has ever been.

I mean, in order to do big, complicated things, you need teams, and teams need to work together. That means much more than just the "hard" skills of individual intelligence, creativity, and discipline. It's also all the "soft" skills, that help the team to retain cohesion, like mutual respect, loyalty, integrity, etc.

The problem is that the example needs to start from the top, and there hasn't been much of a good example, up there, recently.

It's not difficult to imagine people feeling justified in doing bad things to their team, like deliberately writing shoddy code, taking credit for colleagues' work, bailing out, before their bugs come to the surface, or throwing their teammates under the bus.

I always tried to foster a team that had mutual respect, and could focus on common goals, even when everyone had their own motivations and priorities. In my case, it worked, but I know that I was lucky.

Re:Developer sabotaged ex-employer with kill switch that act... by ElFitz on Friday March 07, 2025 @10:21PM (#43297200)
> but I think it's much worse, now, than it has ever been.

At some point, some US employers would hire armed private security companies like Pinkerton to break strikes, often leading to multiple deaths.

In other countries, the army would be sent to break prolonged strikes by shooting at strikers.

In other words, it has been way worse.

Re:Developer sabotaged ex-employer with kill switch that act... by ChrisMarshallNY on Saturday March 08, 2025 @12:16AM (#43297680)
Might be comparing apples to oranges, there.

Those conflicts (and there was a more recent one, in UK, during the 1980s), are with folks that have difficult, low-skill, low-pay, blue-collar jobs that can be filled by many people.

I doubt that you could find similar stuff about high-skill, highly-paid employees, such as engineers. I think that, even in the days when cavalry was being used against striking miners, the white-collar workers were being treated fairly well.

Maybe it has been worse for them, but I’m not so sure.

Re:Developer sabotaged ex-employer with kill switch that act... by pr0zac on Friday March 07, 2025 @10:43PM (#43297305)
> In other countries, the army would be sent to break prolonged strikes by shooting at strikers.

This happened in West Virginia as well: https://en.m.wikipedia.org/wiki/Battle_of_Blair_Mountain

Re:Developer sabotaged ex-employer with kill switch that act... by behringer on Friday March 07, 2025 @10:54PM (#43297355)
Was it worse though? Before they made it obvious. Now it's insidious. They still destroy lives, just the same.
Re:Developer sabotaged ex-employer with kill switch that act... by ranger_danger on Friday March 07, 2025 @09:53PM (#43297087)
I would think making it look like something that _wasn't_ caused by a human would be even smarter.
Re:Developer sabotaged ex-employer with kill switch that act... by throwaway3572 on Friday March 07, 2025 @10:22PM (#43297208)
Interesting. How would that work? Asking for a friend. :)
Re:Developer sabotaged ex-employer with kill switch that act... by olalonde on Friday March 07, 2025 @10:41PM (#43297297)
Something that could plausibly looks like an unintentional bug, but that's a lot harder to come up with.
Re:Developer sabotaged ex-employer with kill switch that act... by woleium on Friday March 07, 2025 @10:30PM (#43297241)
maybe something like a core switch rom failure due to too many writes, then an unplanned reboot at a critical time?
Re:Developer sabotaged ex-employer with kill switch that act... by smitty1e on Friday March 07, 2025 @09:35PM (#43297013)
There are so many little bits of logging going on with modern systems that the idea of totally cleaning up all evidence seems far-fetched.

Not that one couldn't make it very hard to tell, but even circumstantial evidence in the hands of a good prosecutor can deliver a conviction.

Re:Developer sabotaged ex-employer with kill switch that act... by ttyprintk on Sunday March 09, 2025 @10:21AM (#43309229)
Most of the stories in this thread end as quietly as possible.