Late Monday, October 26, a week before the November 3 midterms, the Federal Election Commission’s electronic filing system went dark. For about two days, campaigns, super PACs, and outside groups could not submit the rapid-turnaround disclosures the law requires in the final stretch of an election. This FEC hack campaign finance filing outage deserves attention well beyond politics. It is a clean case study of what happens when a legal deadline keeps running after the platform you file on stops working.
What We Actually Know About the FEC Hack and Campaign Finance Filing Outage
Precision matters here, because the public record is thinner than many headlines suggest. According to Reuters reporting published by NBC News, an FEC electronic filings officer emailed several campaign compliance firms Monday night. The email said: “We have a bad actor attempting to breach FEC systems. As a result, we’ve had to temporarily shut down our web facing services.” The FEC’s own public statement was narrower: “at this time, the FEC’s electronic filing system is currently offline and our IT staff are actively working to restore service.” The agency said previously filed reports remained searchable and otherwise declined to comment.
A status message put the start of the outage at around 10 p.m. ET Monday. CNBC reported that on Tuesday night the FEC said it had identified the issue and was implementing a fix. CNBC also noted that the FEC had not said who was behind the reported breach attempt, whether anyone gained access to its systems, or whether any data was compromised.
By Wednesday, October 28, Reuters reported the system had been restored after being offline for nearly 41 hours “to contain a cyberattack.” Reuters also reported, citing an email, that campaign finance managers had to reset their passwords before logging back in. The FEC did not announce details on the cause, and Reuters could not establish a motive. CISA and the FBI referred questions to the FEC.
So the fair summary is this. An FEC official described an attempted breach, and the agency took its web-facing filing services offline to contain it. As of these reports, there was no public confirmation that attackers got in or that any data was taken. I am not going to claim otherwise.
Why the Timing Hurt
The FEC does not administer elections. Reuters and CNBC both stress that the outage had no effect on voters’ ability to cast ballots. What it hit was transparency. CNBC explains that in the final 20 days before an election, candidate committees must report certain contributions or loans of $1,000 or more within 48 hours. Political committees and outside groups must disclose certain spending within 24 hours.
That window is when the money moves fastest. Brendan Glavin, research director at OpenSecrets, told Reuters that super PACs and dark money groups spent an average of over $50 million per day in the week before the outage, with more than $250 million reported on October 20 alone. “Disclosure delayed is disclosure denied,” OpenSecrets executive director Hilary Braseth said in a statement. Steven Mele, CEO of compliance firm MBA Consulting Group, told Reuters: “I’ve never seen this in 26 years.”
CNBC adds context that should worry anyone who manages public-sector IT. The six-member commission has had just two members since October 2025 and has lacked the four commissioners needed to take official action since May 2025, while career staff keep operations running.
The Containment Call Was Probably Right
Kyle Sandy, cybersecurity director at Logically, told Reuters that taking the system offline is the right call during an attack. “It tells me the FEC detected something they couldn’t immediately scope and chose a known outage over an unknown risk,” he said. I agree. When you cannot yet scope an intrusion attempt, shutting down web-facing services and forcing credential resets is defensible. That is especially true when the integrity of filed records is the whole point of the system.
The hard part is that the rest of the world keeps its own clock. Filers still had legal deadlines. Watchdogs still had a public to inform. That is the gap I want IT leaders to plan for.
My Recommendations: When a Deadline Outlives Your Platform
These are my opinions for IT, compliance, and security teams, not FEC guidance or legal advice.
If You Run the Platform
- Publish an outage protocol before you need it. Filers should know in advance what counts as timely filing when your system is down, and where official updates will appear.
- Separate intake from the public web. Design a degraded mode, such as an authenticated backup submission channel, that you can keep open while you contain an incident on the main portal.
- Plan the credential reset. Forced resets for every filer at once are a support event. Script the communications and staff the help desk before the incident.
- Say what you can, early. Reuters noted that the lack of information fueled conspiracy theories. A short, factual statement on scope and data status narrows the rumor space.
If You Depend on Someone Else’s Platform
- Map your hard deadlines to single points of failure. Any regulatory filing, payment run, or customer notice that depends on one external portal belongs on your risk register.
- Keep evidence of attempted filing. Screenshots, timestamps, error messages, and saved submissions protect you if questions come up later.
- Prepare filings ahead and queue them. Have reports ready to submit the minute service returns, rather than scrambling in the backlog.
- Know your official channels. Decide in advance which agency status page or account you treat as authoritative, and do not act on rumors.
Here is a hypothetical worth a tabletop exercise. Your quarterly regulatory filing is due at midnight, and the agency portal goes offline at 9 p.m. because of a suspected intrusion. Who decides what you do, what do you document, and who tells leadership? If you cannot answer in five minutes, you have homework.
The Bottom Line
Based on what has been reported, this was an attempted breach that forced a deliberate shutdown. It was not a confirmed data theft. The lesson is not unique to campaign finance. Every organization that runs or relies on a deadline-driven platform needs a plan for the hours when security wins and the system stays dark.
