undefined
Posts
undefined
Followers
Whistleblower Says DOGE Facilitated NLRB Data Breach, Covered Tracks
By Markus Kasanmascheff,
2025-05-04A detailed whistleblower disclosure alleges that President Trump’s Department of Government Efficiency (DOGE), led by Elon Musk, compromised systems at the National Labor Relations Board (NLRB) in early March, removing sensitive data while attempting to obscure its actions.
Daniel Berulis, an experienced DevSecOps Architect at the NLRB holding Top Secret/Sensitive Compartmented Information (TS/SCI) clearance, provided the disclosure to Congress and the U.S. Office of Special Counsel on April 14 via the nonprofit Whistleblower Aid .
The account, corroborated by NPR through internal records and interviews , claims DOGE engineers demanded top-level system access, instructed staff not to follow standard logging procedures, and subsequently engaged in activities that triggered alarms. These included suspicious login attempts from Russia using valid credentials created minutes earlier and the apparent shutdown of an internal investigation, with Berulis also reporting direct intimidation. DevSecOps is a practice that integrates security testing and protection continuously throughout the software development and deployment process.
The sequence detailed in Berulis’s sworn declaration began when DOGE personnel arrived at the NLRB headquarters in the first week of March. The NLRB investigates unfair labor practices and stores confidential unionization data, employee PII, and proprietary business information, protected under laws like the Privacy Act .
Berulis asserts DOGE required “tenant owner level” accounts within the NLRB’s Microsoft Azure cloud environment. This level provides unrestricted administrative control over an organization’s entire cloud presence, far exceeding typical user or even high-level administrative needs. Berulis stated instructions were relayed “that there were to be no logs or records made of the accounts created for DOGE employees,” and that staff were told to “stay out of DOGE’s way entirely, and assist them when they asked.” He told NPR, “That was a huge red flag… It violates every core concept of security and best practice.”
Highest Access, No Logs Requested
Following DOGE gaining this access, Berulis documented numerous technical anomalies. Around 3-4 a.m. EST between March 4th and 5th, monitoring tools registered a large, anomalous spike of outbound data traffic, estimated at 10 gigabytes, primarily text files, as first reported by KrebsOnSecurity .
Berulis worried this data could include “sensitive information on unions, ongoing legal cases, and corporate secrets,” potentially including “PII of claimants and respondents with pending matters before the agency, but also many other businesses confidential internal processes and information gathered or provided during investigations and litigation that were not intended for public release.”
Investigation was hampered as logs monitoring outbound traffic were missing, and the network team later reported an inability “to analyze outbound traffic… due to misconfigured or missing tools.” Some actions were attributed only to a “deleted account.”
Berulis also found security controls altered: multi-factor authentication (MFA), which requires multiple proofs of identity, was found disabled for mobile devices in Azure Purview; internal alerting systems were off; the network watcher was inactive; and conditional access policies, rules governing resource access, were changed without approval. He also noted billing spikes related to storage input/output for resources that seemed to have been deleted shortly after creation.
DOGE engineers allegedly used tools facilitating covert activity. Berulis observed the installation of a “container”—an isolated virtual environment that can run programs without easily revealing its activities to the host network. He also documented, via threat hunting tools, three programmatic downloads of external GitHub libraries not used by the NLRB, suggested by the use of a “-noprofile” flag which starts commands with a clean configuration.
One library, linked by KrebsOnSecurity to DOGE employee Marko Elez described as a tool to generate numerous IP addresses for “web scraping and brute forcing” —techniques for automated data extraction and password guessing. Berulis also saw evidence of tools named “requests-ip-rotator” and “browserless” being used.
Additionally, he flagged a public GitHub repository briefly maintained by DOGE engineer Jordan Wick titled “NxGenBdoorExtract,” suggesting a potential tool to extract data from the NLRB’s internal case management system, NxGen . Unknown users also briefly created and deleted a Shared Access Signature (SAS) token , a temporary credential for Azure storage, configured to expire quickly. Berulis initially assumed some anomalies might be connected to internal development teams but later validated this was not the case.
Suspicious Logins and Intimidation
Adding national security concerns, Berulis documented login attempts starting around March 11 from a Russian IP address (83.149.30.186 in Primorskiy Krai, per KrebsOnSecurity). These attempts targeted at least one newly created DOGE account (`DogeSA_2d5c3e0446f9@nlrb.microsoft.com`) and appeared to use the correct username and password, only failing due to NLRB’s policy blocking foreign logins.
The disclosure states many attempts occurred “within 15 minutes of the accounts being created by DOGE engineers.” Berulis also found other suspicious admin accounts with non-standard names like “Whitesox, Chicago M.” and “Dancehall, Jamaica R.” Former FBI cyber official Russ Handorf told NPR, “When you move fast and break stuff, the opportunity to ride the coattails of authorized access is ridiculously easy to achieve.”
The whistleblower’s internal efforts to address the situation reportedly met resistance. After Berulis raised findings with NLRB CIO Prem Aburvasamy, a leadership group formed. Around March 24, the ACIO of Security concluded the events warranted reporting to US-CERT.
However, Berulis asserts that between April 3-4, instructions came “to drop the US-Cert reporting and investigation and we were directed not to move forward or create an official report.” Days later, on April 7, Berulis found a threatening note taped to his door, containing drone-captured photos of him and referencing his disclosure. His attorney, Andrew Bakaj, described it as “targeted, physical intimidation and surveillance.”
Investigation Halted, Wider Concerns Emerge
The NLRB incident reflects broader anxieties about DOGE’s operations. Since early 2025, DOGE has aggressively sought access to sensitive data across government, including Treasury payment systems and OPM personnel files . Reports surfaced of DOGE using AI tools to monitor federal workers and collaborating with Palantir on an IRS “mega API” project potentially using its Foundry data platform. This occurred alongside the reported weakening of CISA , which faced staff cuts and resignations of key leaders .
DOGE’s own technical readiness and personnel choices faced scrutiny, including its insecure public website and the hiring of individuals with controversial backgrounds . Security expert Bruce Schneier warned DOGE’s actions risked becoming a “National cyberattack.” Erie Meyer, the former CFPB CTO, told NPR the NLRB allegations mirrored patterns she saw: “God-tier” access demands, disabling logs, and stonewalling investigations. “I am trembling,” she said upon hearing the NLRB details.
Conflicts and Consequences
Labor law experts emphasized the potential damage if NLRB data were compromised. Former NLRB General Counsel Richard Griffin told NPR, “None of that confidential and deliberative information should ever leave the agency.” Experts highlighted risks to union organizing, exposure of witness testimony, corporate espionage, and the conflict of interest posed by Musk, whose company SpaceX is suing the NLRB . “If they really did get everything, then he has information about the cases the government is building against him,” Harvard Law’s Sharon Block told NPR.
The NLRB initially denied DOGE access or a breach occurred. However, one day after NPR’s story broke, OPB reported DOGE representatives met again at the NLRB on April 16 , and a chairman’s email affirmed compliance with DOGE requests. The White House maintained DOGE’s actions were transparent. Congressional oversight continues; Rep. Gerald Connolly called for IG investigations, and later joined Rep. Lori Trahan in questioning the NLRB Chairman about potential Privacy Act and FISMA violations, noting Congress hadn’t received the required FISMA breach notification. FISMA, the Federal Information Security Modernization Act, mandates reporting major security incidents to Congress within seven days. Berulis told NPR he felt a “moral imperative” to speak out.
The post Whistleblower Says DOGE Facilitated NLRB Data Breach, Covered Tracks appeared first on WinBuzzer .