Twin brothers wipe 96 government databases minutes after being fired

Post by Our_Benefactors » Thu, May 14, 2026, 2:08 AM UTC

profsummergig wrote: post #247

zuzululu wrote: post #164

I'm just amused how these people were even hired to begin with ? They don't seem to be Americans? How were they even allowed to work on sensitive systems? Why was this even allowed? So many questions. At 4:58 pm, he wiped out a Department of Homeland Security database using the command “DROP DATABASE dhsproddb.” At 4:59 pm, he asked an AI tool, “How do i clear system logs from SQL servers after deleting databases?” H…

[flagged]

Post by tardedmeme » Thu, May 14, 2026, 2:16 AM UTC

tempaccount5050 wrote: post #45

scottlamb wrote: post #39

> [Opexus] said that “the individuals responsible for hiring the twins are no longer employed by Opexus.” Getting close to the classic Monty Python line: "Those responsible for sacking the people who have just been sacked, have been sacked." Jokes aside, stuff like this sucks because I suspect many employers will take from it the most extreme, dehumanizing lessons, e.g.: (a) make firings [edit: including lay-offs] as…

When you are talking about access like they had "make firings as abrupt as possible including terminating all access immediately" not doing this is incompetence. This is absolutely a standard and has to be for these kinds of positions. I've never worked anywhere where it wasn't for the majority of IT staff. You meet with HR, someone clears your desk, and security walks you out.

Post by jimmaswell » Thu, May 14, 2026, 2:23 AM UTC

pavel_lishin wrote: post #114

jimmaswell wrote: post #74

Earlier quoted context omitted.

I've never had a job with a permanent individual desk like this. The one in-person real job I had, it was only shared working space that different people used at different times of the day or on different days, and I think you were discouraged from leaving anything. The idea of there being "your desk" with a framed photo of your kids and favorite coffee mug seems like a nearly extinct piece of nostalgia. It must have…

May I ask how long you've been working? I'm in my early 40s, and I've never had a job where we've "hot-desked" like that, even when a company was out-growing an office.

Post by subscribed » Thu, May 14, 2026, 2:57 AM UTC

BrandoElFollito wrote: post #69

giantg2 wrote: post #55

How did they get access to 5k passwords? Are they being sent/stored in cleartext? This is the most baffling part of the article for me. The second part I'm unclear about is how you could pass SOC2 when you aren't terminating account access simultaneously with the employment termination.

And how exactly do you want to store passwords if not in plain text (and then encrypted of course)? 5k is a lot, the authorization process is broken, but this is not related to how the passwords are stored. The only solution is correct access segregation and a bastion

Post by stirfish » Thu, May 14, 2026, 3:12 AM UTC

yaur wrote: post #156

scottlamb wrote: post #39

> [Opexus] said that “the individuals responsible for hiring the twins are no longer employed by Opexus.” Getting close to the classic Monty Python line: "Those responsible for sacking the people who have just been sacked, have been sacked." Jokes aside, stuff like this sucks because I suspect many employers will take from it the most extreme, dehumanizing lessons, e.g.: (a) make firings [edit: including lay-offs] as…

Terminating access and rotating passwords (if needed) while the person is in the meeting but has not yet found out they are being let go has been SOP for at least the last 20 years