Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

DOGE worker’s code supports NLRB whistleblower

krebsonsecurity.com

Post reply on HN
Print view View original

311–320 of 586 posts

Re: DOGE worker’s code supports NLRB whistleblower

#311

Post by cgriswald »

derektank wrote: post #244
sterlind wrote: post #87

Earlier quoted context omitted.

it's written into the Constitution very explicitly. and it's a really bad time to hold a Constitutional Convention.

I'm not actually convinced that now would be a terrible time to hold a constitutional convention. Yes, it would be messy, but the nature of the ratification requirements (3/4 of all states) means that nothing could make it through without essentially unanimous consent of the country as a whole.

While we are at it we can add ranked voting and a vote of no confidence (maybe initiated by congress and voted on by the states or people).

Re: DOGE worker’s code supports NLRB whistleblower

#312

Post by SpicyLemonZest »

declan_roberts wrote: post #254
ThinkBeat wrote: post #136

1. DOGE employees access data they were not supposed to. This fairly clear. The story says that DOGE attained access to an account that had huge permissions into what it could see and alter. The person or persons from DOGE may have downloaded 10GB of data. The person may have used this in a manner that is illegal. Or it is illegal to start with. With the understanding that POTUS may or may not be allowed grand such a…

The author brings up the ip scraping but makes no effort to tie anything together. It's actually really confusing. Were they using this utility to steal the data or are these two just totally unrelated things?

We have no way to know what they were using it for, because as the article details, DOGE works hard to make sure nobody can find out what it's doing or why.

Re: DOGE worker’s code supports NLRB whistleblower

#313

Post by the_optimist »

polalavik wrote: post #50
the_optimist wrote: post #38

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?

I appreciate the question. The most obvious is that this is an “audit the auditors” exercise, and they do not want to leak information toward a likely adversarial counterpart. If they have the authority to so, then they do. An adjacent complaint about “not following Treasury policy is similar.” If these systems exist, there is a governing authority structure, and that does not begin at the level contemplated in this document.

Re: DOGE worker’s code supports NLRB whistleblower

#314

Post by fzeroracer »

jiggawatts wrote: post #58

This is much ado about nothing. The article tries to very hard to make something ordinary sound nefarious. This appears to be DOGE employees simply doing their job. You may not agree with what they’re doing in a political sense, but if you were tasked with the same problem you’d come up with a nearly identical solution. For example: “tenant admin” is probably the special role that can bypass access control (not audit…

> This sounds scary but I regularly request this right from large government departments and I get it granted to me.

Prove it. I want you to give examples of where you did something like this.

Re: DOGE worker’s code supports NLRB whistleblower

#315

Post by Sytten »

icedchai wrote: post #285
timewizard wrote: post #242

Earlier quoted context omitted.

To be fair the code actually creates a new API gateway server that acts as a proxy on to an already existing server and you're possibly meant to use this header with your own gateway service. So, it's set as a header, sent to a user owned proxy, then to the actual external endpoint. On the other hand I think the receiving API Gateway will be able to see and log your AWS account identifier when you do this. So your IP…

The code seems like a "creative" use of API gateway to turn it into a proxy for other external sites (single site, really, since you need one per site.) Wouldn't it be simpler to send the requests through a lambda (with a function URL) and get better control of the outbound requests?

This actually a very common way that hackers have used api gateway for years now.

You can take a look at plugins like IPRotate. We are currently working on bringing that into our product.

Re: DOGE worker’s code supports NLRB whistleblower

#316

Post by Pompidou »

bequanna wrote: post #292
mythrowaway49 wrote: post #263

this part of the whistleblower complaint seem way worse: " On or about March 11, 2025, NxGen metrics indicated abnormal usage at points the prior week. I saw way above baseline response times, and resource utilization showed increased network output above anywhere it had been historically – as far back as I could look. I noted that this lined up closely with the data out event. I also notice increased logins blocked…

This just seems odd. Why would they attempt a login from Russia (if it was indeed Russians)? It is incredibly cheap to use a VPN with a US residential IP.

Maybe not everyone involved is quite the genius you might've been expecting.

Re: DOGE worker’s code supports NLRB whistleblower

#317

Post by grandempire »

ThinkBeat wrote: post #136

1. DOGE employees access data they were not supposed to. This fairly clear. The story says that DOGE attained access to an account that had huge permissions into what it could see and alter. The person or persons from DOGE may have downloaded 10GB of data. The person may have used this in a manner that is illegal. Or it is illegal to start with. With the understanding that POTUS may or may not be allowed grand such a…

> I dont think POTUS can

What data in a federal agency could the chief executive not have authorization to access?

Re: DOGE worker’s code supports NLRB whistleblower

#319

Post by DrillShopper »

plandis wrote: post #101
progbits wrote: post #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…

GPLv3 requires the license to be kept. Seems reportable to the owner of the repo and or GitHub.

I'm sure the people who work for an administration that by and large flaunts court orders responsible for this will get right on that.....aaaand it's gone.

Re: DOGE worker’s code supports NLRB whistleblower

#320

Post by lukev »

tenpies wrote: post #301
stevenwoo wrote: post #287

Earlier quoted context omitted.

Any guesses for best possible interpretion? The Russians have infiltrated their PCs with keyloggers and DOGE are working from insecure open networks. The worst possible interpretation is straightforward - they are working for the Russians as agents and let the Russians in or installed the keyloggers for Russia.

Don't forget the third option: false flag. The objective may not have been to obtain access or any useful data. The objective may have been to get the scary headlines about Russians and use the existing media and political agitprop to further destabilize the government you seek to color revolution away.

I don't follow. Are you saying the DOGE boys are trying to give Trump bad press?
Post reply on HN