Washington, Federal Courts & Cybersecurity
Cyber Incident Halts Federal Bankruptcy Notice Services Nationwide
A contractor breach has taken Bankruptcy Noticing Center systems offline, interrupting the production and distribution of court notices.
A national court service goes offline
A cybersecurity incident affecting BAE Systems Inc. has disrupted the Bankruptcy Noticing Center, according to the Administrative Office of the U.S. Courts. BAE operates the center’s systems and websites for the federal judiciary. The outage has halted production and distribution of bankruptcy notices for courts nationwide. Several related websites, including electronic noticing and creditor-registration services, remain unavailable. The judiciary and contractor say they are coordinating an investigation and restoration work.
Notices protect legal rights
Bankruptcy courts send notices to debtors, creditors and other parties about filings, hearings, deadlines and orders. Timely receipt can determine whether someone files a claim, objects to a proposal or appears in court. The outage therefore has consequences beyond website inconvenience. Courts may need to consider extensions or other relief when a party can show that disrupted service caused prejudice. Local orders and docket entries, not general assumptions, will govern each case.
Some electronic functions continue
The District of Connecticut reported that Notices of Electronic Filing generated through CM/ECF continued to operate, even while Bankruptcy Noticing Center processing and several websites were down. That distinction matters for lawyers and parties deciding how to monitor cases. The center also handles paper and mandatory electronic notices for high-volume recipients. Users should consult the specific court’s official alerts and docket rather than rely on a single service status for every type of communication.
A contractor is part of court infrastructure
The incident demonstrates how federal operations depend on private vendors. Outsourcing can provide specialized technology, but it also extends the security boundary beyond government networks. Contracts should require incident reporting, tested backups, access controls, recovery plans and independent audits. The judiciary should disclose operational effects and remediation without revealing details that would help attackers. BAE’s investigation will need to determine the initial access, affected data and whether unauthorized information was removed.
Users should verify, not improvise
Debtors and creditors should obtain information from official court domains, case dockets and authorized counsel. A disruption can create opportunities for phishing messages that falsely claim a missed deadline or demand payment. Courts do not cure security risk by directing people to unverified links. Users should preserve outage notices, document attempted access and ask the relevant clerk about procedures when a deadline may be affected. Sensitive personal or financial information should not be sent in ordinary email.
Recovery needs a public accounting
The first goal is safe restoration, followed by an accurate review of what failed and how long notice delivery was interrupted. Courts should publish consistent updates and identify whether delayed documents require re-service. After recovery, the judiciary and Congress can examine vendor oversight and continuity funding. No public evidence yet establishes the attacker, method or full data impact. Reporting should keep those questions open until forensic findings or official notifications provide support. A post-incident report should distinguish service availability, data exposure and recovery costs because each requires a different remedy.
Reporting note: This article draws on public records and verified reporting; material claims are attributed in the text.