WASHINGTON, D.C. – A federal judge has extended a temporary restraining order (TRO) blocking representatives of the Department of Government Efficiency (DOGE), led by Elon Musk, from accessing sensitive payment systems within the U.S. Treasury Department.
The ruling, issued by Judge Jeannette Vargas of the U.S. District Court for the Southern District of New York, criticized DOGE’s approach as “chaotic and haphazard.”
This latest decision adds fuel to the ongoing legal battles between the federal government, led by President Donald Trump’s administration, and a coalition of 19 Democratic state attorneys general who argue that Musk’s team poses risks to national data security.
Why Did the Judge Extend the Block?
Judge Vargas kept in place a restraining order that prevents DOGE from accessing any Treasury Department systems containing sensitive personal or financial data. These systems, managed by the Bureau of Fiscal Services (BFS), hold information including:
- Social Security numbers
- Bank account details
- Email addresses
- Home addresses
- Birth dates and places
In her ruling, Vargas said the plaintiffs are likely to succeed in proving that DOGE’s rushed attempts to access BFS systems were “arbitrary and capricious.” She also criticized the urgency pushed by the Trump administration, despite the fact that the executive order establishing DOGE allowed a 30-day window for proper team assembly.
“The inexplicable urgency and time constraints all but ensured that the launch of the Treasury DOGE Team was chaotic and haphazard,” Vargas stated.
The Main Concerns: Data Privacy and Security
The court’s decision highlights deep concerns over how quickly DOGE’s two key representatives, Marko Elez and Thomas H. Krause, Jr., were granted access to sensitive financial systems without thorough vetting. Judge Vargas found:
- No evidence that Elez or Krause went through proper security clearance checks.
- Elez received full access to BFS systems, instead of the more limited read-only access that should have been granted initially.
Cybersecurity experts have also warned of potential security breaches and the mishandling of personal data if access is granted without strict controls.
Next Steps: Treasury Department’s Responsibilities
The Treasury Department now has until March 24 to meet several conditions set by Judge Vargas. The department must submit a report confirming:
- Proper training for DOGE representatives regarding BFS system access.
- Completion of security clearance procedures for all DOGE members.
- Implementation of risk mitigation strategies to safeguard sensitive data.
- Establishment of clear reporting chains to ensure accountability within Treasury.
This report aims to reassure both the court and the public that DOGE’s access will not compromise the security of Americans’ financial information.
Political and Legal Fallout
DOGE’s rapid and unregulated access attempts have triggered a wave of legal and political backlash:
- A coalition of union groups has sued the Treasury Department and Treasury Secretary Scott Bessent to block DOGE’s access altogether.
- Over 140 House Democrats introduced a bill designed to prevent “unlawful” access to the BFS systems by DOGE associates.
- The Treasury Office of Inspector General has announced a formal audit of DOGE’s actions and system access.
Democratic attorneys general argue that granting DOGE unrestricted access, particularly under Musk’s leadership, violates constitutional limits on executive authority and poses a direct threat to the privacy of millions of Americans.
The Role of Elon Musk and Trump’s Executive Order
President Trump created DOGE through an executive order on January 20 to oversee government efficiency, reduce bureaucracy, and cut wasteful spending. The administration appointed Musk to lead the initiative, with the expectation that his reputation for disruption and innovation would streamline government operations.
However, critics argue that Musk’s aggressive approach, combined with the Trump administration’s pressure for rapid action, led to the rushed and legally questionable access attempts.
