**EXCLUSIVE: CISA Caught Scrubbing "Leaked" GitHub Data – But Who Leaked It? Whistleblower Says It Was an Inside Job to "Protect the Narrative"**
EXCLUSIVE: CISA Caught Scrubbing “Leaked” GitHub Data – But Who Leaked It? Whistleblower Says It Was an Inside Job to “Protect the Narrative”
Washington, D.C. – In a move that has cybersecurity experts and transparency watchdogs raising eyebrows, the Cybersecurity and Infrastructure Security Agency (CISA) has quietly purged a massive trove of allegedly “exposed” data from the GitHub repositories of multiple federal contractors. The official narrative from CISA? A routine “hygiene” sweep to prevent foreign adversaries from exploiting sensitive network blueprints.
But a source with direct knowledge of the purge is telling a very different story.
“They’re not protecting us. They’re protecting the story,” the whistleblower, who spoke on condition of anonymity for fear of retaliation, told this outlet. “This wasn’t a leak from a careless developer. This was an intentional data dump—engineered to look like a sloppy mistake—designed to test a specific narrative in the wild: that critical infrastructure is dangerously exposed.”
The data in question, purportedly from a Department of Energy sub-contractor, contained detailed network topology maps and authentication scripts for a major East Coast power grid. While CISA claims the data was “publicly discoverable” for weeks, our analysis of commit timestamps shows the repository was created only 72 hours before CISA’s takedown request.
Who benefits?
Critics point to a perfect political storm. With the current administration pushing for a massive expansion of CISA’s domestic surveillance and enforcement powers, a high-profile “near-miss” involving a foreign state actor would be a legislative gift.
“They need a boogeyman to sell the ‘Big Tech’ oversight bill,” said former NSA analyst and privacy advocate Jenna Ortiz. “You manufacture a near-catastrophe, you ‘heroically’ respond, and suddenly everyone forgets you’re asking for