Executive SummaryA cybersecurity incident affecting BAE Systems has resulted in a nationwide disruption of the US federal bankruptcy court notification process. The incident, first impacting systems as early as October 9, 2026, led to the outage of the Bankruptcy Noticing Center (BNC) systems and associated websites operated by BAE Systems on behalf of the US Judiciary. As a result, the production and distribution of bankruptcy notices have been halted, affecting both electronic and paper notifications across all US bankruptcy courts. There is no public evidence at this time of data exfiltration or compromise of sensitive information. Both BAE Systems and the Administrative Office of the US Courts (AOUSC) have confirmed the incident and are actively investigating and working to restore operations. The incident underscores the critical dependency of legal infrastructure on third-party vendors and highlights the ongoing need for robust cybersecurity measures in the public sector.Technical InformationThe security incident involving BAE Systems has had a significant operational impact on the US federal judiciary’s bankruptcy notification process. The Bankruptcy Noticing Center (BNC), managed by BAE Systems for the AOUSC, is responsible for the electronic and paper distribution of bankruptcy notices to creditors and other parties. On or before October 9, 2026, a cybersecurity incident led to the immediate shutdown of all BNC-operated systems and websites, including bnc[.]uscourts[.]gov, bankruptcynotices[.]uscourts[.]gov, notices[.]uscourts[.]gov, and the National Creditor Registration Service (BleepingComputer, The Register, ABA Journal).The AOUSC and BAE Systems have both issued statements confirming the incident, its scope, and ongoing remediation efforts. The incident is described as a “cybersecurity incident” isolated to the BNC system, with no public confirmation of ransomware, data theft, or specific attack vectors as of October 16, 2026. The affected courts continue to accept filings and process documents, but delays in the entry and service of notices and orders are expected. The Eastern District of Texas issued a general order extending certain deadlines due to the outage (The Register).No technical details regarding the attack vector, malware, or tools used have been publicly disclosed. There is no confirmation of data exfiltration, and no indicators of compromise (IOCs) beyond the affected domains have been reported. The incident is currently under investigation by both BAE Systems and the AOUSC.Historically, the US federal judiciary has been targeted by multiple cyberattacks, including the 2025 breach of the CM/ECF electronic case management system and PACER, as well as attacks on the FBI and Arizona Judicial Branch in September 2026. However, there is no evidence directly linking this incident to any known threat actor or campaign. The only confirmed impact is a denial of service (DoS) on critical court notification infrastructure, but the method (e.g., ransomware, network intrusion, supply chain compromise) is not disclosed.The incident highlights the vulnerability of critical legal infrastructure to third-party vendor breaches and underscores the importance of robust third-party risk management and incident response planning.Affected Versions & TimelineThe systems affected are the Bankruptcy Noticing Center (BNC) systems and associated websites operated by BAE Systems for the US Judiciary. The outage began as early as October 9, 2026, with public disclosure and official statements made on October 16, 2026 (BleepingComputer, The Register, ABA Journal). The affected systems include bnc[.]uscourts[.]gov, bankruptcynotices[.]uscourts[.]gov, notices[.]uscourts[.]gov, and the National Creditor Registration Service. The incident has halted the production and distribution of bankruptcy notices for all US bankruptcy courts and affected the ability to process both electronic and paper bankruptcy notices nationwide.Threat ActivityAs of the latest reporting, there is no public evidence of specific threat actor attribution, malware, or tools used in the incident. The incident is described as a “cybersecurity incident” isolated to the BNC system, with no confirmation of ransomware, data exfiltration, or specific tactics, techniques, and procedures (TTPs). The only technical artifacts available are the affected domains. The US federal judiciary has previously been targeted by sophisticated cyberattacks, but there is no evidence directly linking this incident to any known threat actor or campaign. All attribution claims would be circumstantial and unsupported by primary technical evidence at this time.Mitigation & WorkaroundsThe following mitigation and workaround recommendations are prioritized by severity:Critical: Organizations relying on the BNC system for bankruptcy notifications should monitor official communications from the AOUSC and affected courts for updates on system restoration and alternative notification procedures. Legal teams should review court orders, such as those from the Eastern District of Texas, for deadline extensions and procedural changes.High: Third-party risk management processes should be reviewed and strengthened, with a focus on critical vendors providing essential legal or operational services. Incident response plans should be updated to account for the potential loss of third-party services and to ensure continuity of operations.Medium: Organizations should assess their own exposure to the affected systems and consider implementing additional monitoring for suspicious activity related to the affected domains. Communication plans should be updated to inform stakeholders of potential delays in bankruptcy notifications.Low: Continue to monitor public sources and official statements for updates on the investigation and restoration of services. Review and update cybersecurity awareness training to include the risks associated with third-party vendor dependencies.Indicators of CompromiseThe following indicators are provided as a point-in-time reference and should be validated before enforcement in security controls. These indicators are limited to the affected domains as no additional technical artifacts have been publicly disclosed.TypeIndicatorReported (date)Source Domainbankruptcynotices[.]uscourts[.]gov2026-10-16https://www.bleepingcomputer.com/news/security/bae-systems-cyberattack-disrupts-us-federal-court-operations/Domainbnc[.]uscourts[.]gov2026-10-16https://www.bleepingcomputer.com/news/security/bae-systems-cyberattack-disrupts-us-federal-court-operations/Domainnotices[.]uscourts[.]gov2026-10-16https://www.bleepingcomputer.com/news/security/bae-systems-cyberattack-disrupts-us-federal-court-operations/Referenceshttps://www.bleepingcomputer.com/news/security/bae-systems-cyberattack-disrupts-us-federal-court-operations/ https://www.theregister.com/security/2026/10/16/attack-on-bae-managed-system-disrupts-us-bankruptcy-courts/5303487 https://www.abajournal.com/news/article/cybersecurity-incident-disrupts-federal-bankruptcy-courtsAbout RescanaRescana provides a third-party risk management (TPRM) platform designed to help organizations identify, assess, and monitor risks associated with external vendors and service providers. Our platform enables continuous monitoring of vendor security posture, supports incident response workflows, and assists in maintaining compliance with regulatory requirements. For questions or further information, please contact us at info@rescana.com.
——————————————————-
Click Here For The Original Source.
