Live data from Hacker News

DOGE worker’s code supports NLRB whistleblower

krebsonsecurity.com

41–50 of 586 posts

Re: DOGE worker’s code supports NLRB whistleblower

#41
post #27

Earlier quoted context omitted.

There isn't one. Anything musk's dogs claim to find cannot be taken at face value because of this. Because there is no audit, and no evidence that they can offer that they didn't doctor their findings. The next time they claim that a 170-year old person is receiving SS checks, they have no way to prove that they didn't subtract a century from that person's birthdate in some table.

Ah, this is something I haven't thought of before. This might not actually be spying, but instead just an attempt to plant fake results.

And even if it's not and everyone involved is a qualified, thoughtful, unimpeachable public servant with no agenda but the general welfare of the Glorious Republic of Arstotzka in their hearts, the lack of an audit trail means that you have to seriously consider that they aren't.

Of course, given the blatant dishonesty and criminality that the rest of this administration is producing (see: every immigration law case that they are losing in court), you'd have to be a useful idiot to actually assume good intent from them.

Re: DOGE worker’s code supports NLRB whistleblower

#42

So what exactly is being alleged here? That these DOGE bros wrote and used “hacker” code from GitHub to bypass security limitations on NLRB data? Why would they even need to do that if they had superuser accounts in the system already?

I think the point of the article is that the whistleblower's original claims can be substantiated publicly. It's another datapoint indicating that the DOGE people are operating haphazardly at the absolute best and, more likely, attempting to obscure their tracks because they know that what they're doing wouldn't pass legal muster.

Re: DOGE worker’s code supports NLRB whistleblower

#43

Earlier quoted context omitted.

Explain please.

Sensitive government data was (sure, allegedly) extracted to Russia via an account that was expressly created to hide / not create logs. This is treason. Allegedly.

This administration is doing a lot of things that are borderline treasonous. Hopefully they get prosecuted when they get voted out or ideally get removed form power.

Re: DOGE worker’s code supports NLRB whistleblower

#45
> Ge0rg3’s code is “open source,” in that anyone can copy it and reuse it non-commercially. As it happens, there is a newer version of this project that was derived or “forked” from Ge0rg3’s code — called “async-ip-rotator” — and it was committed to GitHub in January 2025 by DOGE captain Marko Elez.

Original code: https://github.com/Ge0rg3/requests-ip-rotator

Forked: https://github.com/markoelez/async-ip-rotator

Code is pretty much the same, with comments removed, some `async` sprinkled in and minor changes (I bet this was just pasted into LLM with prompt to make it async, but if that worked why not).

Except... Original GPL3 license is gone. Obviously not something you would expect DOGE people to understand or respect.

Re: DOGE worker’s code supports NLRB whistleblower

#46
I find the following bizarre. Ignoring who this marko guy is, why would a random person post such a "take down" of the repo? I have never randomly passed by a repo and wanted to just dunk on it. Also this critique reeks of being AI generated.

> On February 6, someone posted a lengthy and detailed critique of Elez’s code on the GitHub “issues” page for async-ip-rotator, calling it “insecure, unscalable and a fundamental engineering failure.”

Link from quote: https://github.com/markoelez/async-ip-rotator/issues/1

The follow comment is interesting to be a coincidental, such a weird interaction.

Re: DOGE worker’s code supports NLRB whistleblower

#47

So what exactly is being alleged here? That these DOGE bros wrote and used “hacker” code from GitHub to bypass security limitations on NLRB data? Why would they even need to do that if they had superuser accounts in the system already?

The article is written very poorly. The disclosure itself is far more readable.

https://whistlebloweraid.org/wp-content/uploads/2025/04/2025...

Re: DOGE worker’s code supports NLRB whistleblower

#48
post #41

Earlier quoted context omitted.

Ah, this is something I haven't thought of before. This might not actually be spying, but instead just an attempt to plant fake results.

And even if it's not and everyone involved is a qualified, thoughtful, unimpeachable public servant with no agenda but the general welfare of the Glorious Republic of Arstotzka in their hearts, the lack of an audit trail means that you have to seriously consider that they aren't. Of course, given the blatant dishonesty and criminality that the rest of this administration is producing (see: every immigration law case…

Of course, it just never occurred to me that there's a less bad but still terrible explanation for ghost admin access.

Re: DOGE worker’s code supports NLRB whistleblower

#49

The fact that they left these packages public on GitHub.. guys you do know you can make things private right? Just shows how dumb these people are honestly

Or they are emboldened in knowing there will be absolutely no consequences. Go look at the list of pardons this administration has handed out. These guys won’t even be charged.

Or they think what they're doing is righteous and they're proud of it. It isn't - DOGE is responsible for hundreds of thousands of deaths through cuts to health programs - but I suspect they are deluding themselves into thinking it is.

Re: DOGE worker’s code supports NLRB whistleblower

#50

For those genuine actors here: this theoretical outrage assumes the premise of something immoral or illegal, and completely ignores the authority structure. This looks and smells like an info operation.

Just, as an exercise, list out 3 good reasons someone might want untraceable admin accounts then list 3 really bad reasons they might want that. If you manage to find 3 good reasons does the outcome of those those outweigh the risks of the potential bad reasons?
Post reply on HN