NorthBay Health’s IT disruption affected patient services in Fairfield and Vacaville, California, in April 2024. The health system acknowledged a cybersecurity incident and said staff were caring for patients through downtime procedures.
Analyst assessment
NorthBay’s notice filed with Massachusetts regulators identifies suspicious network activity Feb. 23, 2024. Its investigation found unauthorized access to certain files between Jan. 11 and April 1. That access window is distinct from the later documented clinical disruption.
The notice says the information varied by individual. It may have included identity and financial information, medical and insurance information, biometrics, account credentials and payment-card details. NorthBay said it did not believe the information had been misused for identity theft or fraud and offered recipients two years of Experian credit monitoring. The sample leaves its mailing date blank.
Operational significance
Local reporting syndicated by KRDO documents a patient’s difficulty reaching the VacaValley walk-in X-ray service April 1 and her unsuccessful visit the following morning. Staff could not check her in or access her records. This is a specific interruption of access to care; it does not establish an emergency-department closure or patient injury.
Becker’s April 3 report quotes NorthBay’s April 2 acknowledgment, describes continuing restoration work and reports that its website was down. These effects concern the wider health system as well as VacaValley Hospital. The parent system and hospital remain distinct linked organizations.
Confidence and uncertainty
Cyber involvement and operational disruption are well supported. SecurityWeek’s January 2025 report describes at least two weeks of disruption, but acknowledges that NorthBay did not specifically confirm ransomware. A shutdown alone cannot establish ransomware or a ransom payment.
The Record reported an Embargo claim. Its linked April 22, 2024, Hackmanac post says NorthBay had been listed on Embargo’s leak site and that the listing was later removed. The post includes an image naming northbay.org. This contradicts SecurityWeek’s statement that no group claimed the attack, but does not establish the actor’s responsibility, encryption or payment. Removal from a leak site is not evidence that a ransom was paid.
SecurityWeek attributes a count of 569,012 affected people to a Maine filing. Its one-year monitoring statement differs from the adult notice’s two-year offer; terms may differ among notices.
Analytic gaps
The entry method, exact application downtime, complete restoration date and any extortion remain unresolved. The incident remains presumed resolved with no verified end date. Later data notifications do not establish continuing clinical downtime. The notice is undated, and the earliest public chronology remains incomplete.