Cybersecurity

Ochsner Health Confirms September Data Breach After Vortex Claims 466 GB of Data

Published By Shivam Sharma8 min read
Ochsner Medical Center in Jefferson, Louisiana, after the health system confirmed a September data breach

Ochsner Health has confirmed unauthorised access to two employee accounts in September, and the timing tells its own story. An unauthorised party got into the accounts between 18 and 21 September and downloaded files from one of them. Ochsner learned of the incident on 1 October. It did not determine what information had been accessed until 18 November. Notification to affected people began on 19 November, 62 days after the first access. Vortex had listed Ochsner on its leak site on 19 November, claiming it held 466 GB of the health system’s Microsoft 365 data, hours before the confirmation reached the public. Whether the confirmed breach and the Vortex claim are the same incident is not established. No source says so, and Ochsner’s notice does not mention Vortex at all.

What Ochsner confirmed

Ochsner Health, which describes itself as Louisiana’s leading non-profit health system, has 47 hospitals, more than 370 health and urgent care centres, over 4,900 employed or affiliated physicians, and more than 40,000 team members. Its notice, published on its website on 19 November and reported by Becker’s Hospital Review and Louisiana First News, says an unauthorised party accessed two employee accounts between 18 and 21 September 2026 and downloaded files from one of them. Ochsner learned of the incident on 1 October and launched an investigation with a third-party forensic firm. On 18 November it determined that specific information had been accessed. The information varies by individual and may include names, demographic information, Social Security numbers and health information.

The incident was limited to Ochsner’s Microsoft environment. It did not disrupt patient care, its Epic electronic health record, MyOchsner or MyChart, or other systems. Ochsner began notifying individuals on 19 November and will mail letters to those whose information is determined to have been involved. It is offering one year of complimentary credit monitoring to individuals whose Social Security numbers were involved. A dedicated line opens on Friday 20 November: 844-971-8661, Monday to Friday, 8 a.m. to 5:30 p.m. Central Time, excluding major US holidays.

NOLA.com reported Ochsner’s confirmation at 02:45 GMT on 20 November. That was 16 hours and 11 minutes after the Vortex listing was discovered at 10:34 UTC on 19 November. Attorneys were already investigating the hackers’ claims before the confirmation: ClassAction.org published its investigation note on 19 November, between the listing and the confirmation.

The 62 days from access to notification

The dates Ochsner has given reconstruct into a long, slow timeline. The unauthorised access ran from 18 to 21 September. Ochsner learned of the incident on 1 October, 13 days after the access began. It took another 48 days, until 18 November, to determine what information had been accessed. Notification began the next day, 19 November, which is 49 days after discovery and 62 days after the first access, or 59 days if counted from the last day of the access window.

That is a long time for people whose Social Security numbers and health information may have been taken to wait without knowing. It is also, on the available record, not unusual for this health system. Ochsner’s earlier breach at Ochsner LSU Health Regional Urology followed a similar shape: unauthorised access from on or about 5 October 2025, detected on 10 October, and publicly disclosed in December 2025, about two months later. The detection was faster that time, five days against 13, but the public disclosure still took roughly two months.

There is a second clock worth noting. The Vortex listing appeared on 19 November. Ochsner’s confirmation reached the public, through NOLA.com, 16 hours and 11 minutes later. The September breach had been known inside Ochsner since 1 October. The confirmation reached the public on 20 November, a day after the Vortex listing appeared. That does not prove the claim caused the confirmation, and this article does not assert that. But the sequence is the sequence: seven weeks of internal knowledge, then a public listing, then a public confirmation within a day.

The Vortex claim, and what it is not

Vortex added Ochsner to its leak site on 19 November. The listing was discovered by ransomware.live at 10:34 UTC, with a “data held” designation, meaning the group claims to have the data in hand, not that it has published it. The claim, as mirrored by trackers, describes a full capture of Ochsner’s Microsoft 365 environment: 24,977 files totalling 466.44 GB, organised as one SharePoint site per system or program, including a Workday expansion project site of 6,439 files and 280.01 GB, plus sites associated with Epic, the electronic health record platform. These are the attacker’s own figures, repeated by trackers. They are not independently verified measurements, and this article does not present them as confirmed theft.

The shape of the claimed numbers is worth examining, with the caveat stated plainly: if the attacker’s numbers are invented, so is this shape. The Workday expansion site is 60.0 percent of the claimed volume but only 25.8 percent of the claimed files. Its files average about 43.5 MB each, against about 10.1 MB for the rest of the claimed haul and about 18.7 MB overall, roughly 4.3 times larger. That profile is consistent with large project archives or data dumps, though file size alone does not prove what the files contain. The Workday expansion project description identifies that site as project-related, but it does not establish what the rest of the claimed collection contains, and it is a concrete reason to doubt any assumption that 466 GB equals 466 GB of patient records.

That doubt is reinforced by what the reporting reviewed did not provide. UnderCode News reports the listing does not include patient-record samples, and the reporting reviewed provided no independently verified evidence that clinical databases were accessed. Epic-related project material is not patient medical records, and nothing in the reported listing shows clinical databases or production EHR systems were accessed. Ochsner’s own notice, for its part, says the incident was limited to its Microsoft environment and did not disrupt its Epic system. Ochsner’s notice does not mention Vortex at all.

Whether the September breach Ochsner confirmed is the same incident as the Vortex claim is not established by any source. There is a timing tension: ransomware.live records the Vortex listing as discovered on 19 November 2026, while Ochsner’s confirmed breach was in September. The listing date is not necessarily the attack date, it may reflect when the claim was published, so the two may be the same incident surfacing months later, or two different incidents. Do not assume a link. The article states the connection is unconfirmed, and it stays unconfirmed until a source establishes it.

Three things are still missing entirely. No affected-individual count has been given by Ochsner, by any regulator, or by Vortex. Becker’s states explicitly that the health system has not disclosed how many individuals were affected. How the unauthorised party gained access to the two accounts has not been disclosed either. And whether any of the claimed 466.44 GB has been leaked or published, as opposed to held, has not been reported.

Two Ochsner breaches, two different stories

Ochsner LSU Health, a separate organisation in the same group, reported a breach about a year earlier, and the two are different animals. The October 2025 incident at Ochsner LSU Health Regional Urology in Shreveport involved retired systems that had been decommissioned in late 2022. An unauthorised third party had access from on or about 5 October 2025 and downloaded files containing names, Social Security numbers, dates of birth, medical record numbers and care information for treatment received before 31 December 2022. It affected up to 4,519 patients. The breach was confined to the retired systems, no other Ochsner LSU Health systems or Ochsner Health locations were impacted, and it caused no disruption to clinical operations.

That incident produced a class-action settlement, Clark v. Regional Urology, with a claim deadline of 16 November 2026, now passed. Payouts were a flat $40 or up to $5,000 with documented losses. The final approval hearing was set for 19 October, and no ruling had been posted as of 20 October. The current incident is different: no patient count, no patient-record evidence, and the confirmed incident is unauthorised access to two employee accounts within Ochsner’s Microsoft environment, while the confirmed patient-data breach sits with the separate LSU affiliate a year earlier. The two should not be conflated, and this article keeps them apart.

There is also no entry in the US Department of Health and Human Services breach portal for a 2026 breach of the main Ochsner Health system, as mirrored on 19 November. The only Ochsner entries are a 2012 archived loss or theft affecting 2,088 individuals and the Regional Urology entry. A portal entry may follow, since notification has only just begun.

What should I do if I am an Ochsner patient?

If you are an Ochsner patient or employee, watch for a letter from Ochsner. Notification began on 19 November, and letters will go to people whose information is determined to have been involved. If your Social Security number was involved, Ochsner is offering one year of complimentary credit monitoring. The dedicated line is 844-971-8661, open Monday to Friday, 8 a.m. to 5:30 p.m. Central Time.

1. Watch for Ochsner’s letter and read it for which of your details were involved.

2. Call 844-971-8661 if you have questions or want to enrol in credit monitoring.

3. Place a fraud alert or credit freeze with the three credit bureaus if your Social Security number was involved.

4. Review your explanation of benefits and MyChart statements for care you did not receive.

5. Do not pay anyone who contacts you claiming to be Ochsner and asking for payment or credentials.

What to watch next

Whether Ochsner discloses how many individuals were affected. Whether the HHS breach portal gains an entry for the 2026 incident, and what number it carries. Whether Ochsner says how the two accounts were accessed. Whether anyone establishes that the Vortex claim and the confirmed September breach are the same incident, or that they are not. And whether any of the claimed 466 GB appears publicly, which would change the story from a confirmed breach with an unconfirmed claim into something larger.