A source with direct knowledge of the situation informs me:
Senior IT staff confirmed that Marko has read and write access. This is no longer a point of doubt.
The white house continues to dispute this and the mainstream press continues to largely report the “read only” factoid, which as I pointed out in my piece this morning is somewhat of a red-herring. However, I have reason to believe the tide will turn (at least somewhat) on this soon.
It is also interesting that they won’t comment or name Marko Elez, only Tom Krause. The Treasury letter from yesterday describes him as:
Mr. Krause is a longtime technology executive. His decades of experience [blah blah blah —lambert]
A source familiar with the situation reports to me that:
The fact that Treasury only talked about Krause shows they’re trying to protect Marko. They are also doing a lot more to protect Marko. As an example: there is a gag order on BFS IT personnel right now. They are not permitted to discuss “DOGE”, even in discussions internal to the Bureau. I have never seen anything like this before.
Marko Elez’s unchecked behavior throughout the most sensitive payments infrastructure in the United States is something they are working very hard to protect.
It has been reported by Josh Marshall at Turning Points [sic] Memo that source code is already being changed. I can’t confirm that reporting from my sources but I can confirm source code changes are being actively pursued. A source informs me:
Thomas Krause and Marko Elez are having discussions about [Payment Automation Manager (PAM)] source code changes. Other people are in the conversation as well. I have no other details about this.
Source code changes are of course an extremely dangerous scenario.
Add new comment