← BACK TO FEED
cybersecurityBAE Systemsbankruptcy courtsdata breachfederal judiciary

BAE Systems Brings Bankruptcy Noticing Center Back Online, Stays Quiet on What Actually Happened

BAE Systems has restored the federal judiciary's Bankruptcy Noticing Center (BNC) after a cybersecurity incident took it offline for over two weeks, stating that no data was extracted and no personally identifiable information was breached. The BNC, which handles notices for all US federal bankruptcy courts, went down around October 9, prompting the Judicial Conference to declare a "Bankruptcy Rules emergency" to allow judges to extend deadlines. The cause of the incident has not been disclosed, and no ransomware or cybercrime group has claimed responsibility.

BAE Systems has restored the federal bankruptcy courts' noticing system after a two-week outage, and is now saying no data left the building.

"BAE Systems, Inc., working closely with the Administrative Office of the U.S. Courts, has resumed operations of the Bankruptcy Noticing Center system. No other systems were affected. No data was extracted. There was no breach of any PII," a company spokesperson confirmed to SecurityWeek.

The Bankruptcy Noticing Center is the single pipeline through which every federal bankruptcy court in the US pushes out its official notices. BAE runs it under contract with the judiciary. That pipeline went dark around October 9, and notices simply stopped moving.

The center came back up on October 26 and started working through the backlog, oldest notices first. The Administrative Office of the US Courts publicly confirmed the restoration the following day.

With two weeks of notices piling up, the Judicial Conference stepped in on October 22 and declared a "Bankruptcy Rules emergency" -- a formal mechanism that lets bankruptcy judges extend deadlines and suspend time periods to manage the downstream chaos.

What BAE still has not told anyone is what actually caused the incident. The company has not said whether this was a cyberattack, an infrastructure failure, or something else entirely. The clean "no data extracted" line is reassuring if true, but it would carry more weight if accompanied by any explanation of what the incident actually was.

No ransomware group has claimed responsibility, which is either good news or just means whoever was responsible is being unusually quiet.

READ NEXT
BAE Systems Breach Knocks Out US Bankruptcy Court Notifications NationwideGMO Puts $1 Million on the Table to Catch Hackers Who Raided Its FX Cloud ServiceQuest Diagnostics Hit by Cyber Breach, Patient Records Exposed