One vendor, one breach: why federal bankruptcy notices stopped nationwide

A cyberattack on contractor BAE Systems has knocked out the Bankruptcy Noticing Center, the system that produces and transmits bankruptcy notices for every federal bankruptcy court in the country. The Administrative Office of the U.S. Courts said access to BNC systems and the websites BAE operates for the judiciary — bnc.uscourts.gov, bankruptcynotices.uscourts.gov, notices.uscourts.gov, and the National Creditor Registration Service — is unavailable, and all production of bankruptcy notices has halted.

The Administrative Office published its statement Thursday afternoon. It did not give a date for the incident, and the record so far does not establish when the intrusion began or how long the outage has run. The office said it is in communication with impacted courts and coordinating with BAE Systems, which it described as actively investigating and working to restore operations. Only one outlet, therecord.media, has reported the event; no other outlet has confirmed it.

That is the whole of the corroborated record, and it is worth being precise about what it does and does not support. It supports a supply-chain failure: a single outside vendor, operating a single shared platform, is the point at which nationwide notice production stopped. It does not support the framing of a nationwide attack on the courts' own systems. It also does not support claims circulating about the number of state courts affected, whether data was exfiltrated, whether a ransom was demanded, or who carried out the intrusion. None of that has been confirmed.

The practical stakes are administrative, not abstract. Bankruptcy notices are the formal machinery that tells creditors, debtors, and trustees what is happening in a case. When that pipeline stops nationwide, filing deadlines, creditor rights, and case administration can be thrown into doubt across every federal bankruptcy court at once. Courts have not said what contingency process, if any, they are using to issue notices in the meantime.

• Treat third-party noticing and document-delivery vendors as tier-one dependencies. Map every court or agency function that routes through a single contractor, and identify which ones have no manual fallback.
• Build and test an offline notice path now. If production halts, courts need a documented interim process for issuing time-sensitive notices rather than improvising one mid-outage.
• Require contractual incident-response terms from vendors: notification timelines, forensic access, and restoration commitments. The judiciary is currently dependent on BAE's own investigation for its understanding of the event.
• Monitor the affected domains and BAE-operated judiciary endpoints for restoration and for any change in behavior when service resumes.
• Watch for follow-on fraud. A notice outage creates a window in which debtors and creditors cannot verify case activity through the normal channel, which is exactly the condition phishing and impersonation campaigns exploit.