Data Breach Response / Eskenazi Health · Updated September 26, 2026 Independent coverage, not a communication from Eskenazi Health

Eskenazi Health Data Breach: What Happened and What You Should Do

Eskenazi Health disclosed a data breach affecting an unconfirmed number of people. Here's what is currently known about the incident, what information may have been exposed, and steps you can consider taking.

Notification / monitoring offer underway Sources listed below
Breach snapshotUpdated September 26, 2026
Company
Eskenazi Health
People affected
Undisclosed

Company notice does not state a headcount.

Incident date
June 3, 2026 – July 27, 2026 (unauthorized access window)
Discovered
July 27, 2026
Disclosed
September 25, 2026 (company incident notice posted)
Information exposed
Status
Notification / monitoring offer underway

Public notice September 25, 2026; individual letters include monitoring enrollment steps.

What happened in the Eskenazi Health breach?

How the attacker got in

Phishing-led unauthorized access to an employee cloud-based work email account (June 3–July 27, 2026).

Timeline of what is known

  1. 01June 3, 2026 – July 27, 2026 (unauthorized access window)Unauthorized access
  2. 02July 27, 2026Breach discovered
  3. 03September 25, 2026 (company incident notice posted)Breach disclosed publicly
  4. 04Individual letters (enrollment instructions included); public notice September 25, 2026Affected individuals notified

Dates come from the sources listed at the bottom of this page. Separate events are kept separate; where a date has not been disclosed, it says so.

What information was exposed?

The categories below come from Eskenazi Health's disclosure and the sources listed on this page. Each is labeled by what the evidence supports. Categories not mentioned in any source are not listed, even if they are common in similar breaches.

Exposed May have been exposed Access not confirmed

The company has not yet disclosed which categories of information were involved.

Why this information matters

The risks below are the ones associated with the categories of information involved in this breach. This describes how exposed information can be used in general. It does not state that any of this has happened with data from this incident.

Information from one breach can sometimes be combined with information from other breaches or public sources. A name and email address on their own are limited. Paired with a date of birth from one leak and an address from a people-search site, they become enough to answer a security question or make a scam call sound informed.

Whether the data from this breach has been sold, shared, or used is not known unless a source on this page says so. Where that is documented, it appears in the "What happened" section above.

If you were affected, consider doing these things now

Practical steps for this breach, in rough order of priority. None of these require buying anything. Monitoring services, including ours, are one option among several.

  1. 01Follow identity-protection enrollment steps in your Eskenazi Health letter.
  2. 02Call 833-918-4281 (Monday–Friday, 9 a.m.–9 p.m. EST) and provide Engagement Number B172612.
  3. 03Review credit reports and financial accounts for activity you do not recognize.
  4. 04Watch for phishing that references Eskenazi Health, HHC, or this incident.
  5. 05Verify any call or email about the breach using the phone number in your written notice.

AI Protection

Monitoring, removal, and recovery help for what comes after a breach.

A breach puts information you can't take back into circulation. AI Protection watches for it being misused, reduces what else can be found about you, and helps you recover if something goes wrong. It cannot undo the breach or retrieve data an attacker already holds.

Get AI Protection Plans from $7 per month. Cancel anytime.

How one breach can contribute to a larger exposure footprint

A possible risk pattern, not a description of this incident. Each step is something that can happen after a breach. Nothing here states that it has happened with data from this incident.

Illustrative pattern
  1. Step 1

    One breach

    A single company's records are accessed without authorization.

  2. Step 2

    Personal information is exposed

    Some categories can be changed afterward. Others, like a name or date of birth, can't.

  3. Step 3

    It may remain accessible

    Copies of breached data can persist well beyond the original incident.

  4. Step 4

    Sources can be combined

    Fragments from different breaches and public sources may be assembled into a fuller profile.

  5. Step 5

    More targeted attempts

    A fuller profile can make fraud, impersonation, phishing, or social engineering attempts more convincing.

A breach is an event. Exposure can last longer.

A password can be reset and a card reissued. Some information can't be replaced, and that is the part that stays useful to someone attempting fraud later. This does not mean fraud will occur. It means the risk does not close when the news cycle does.

Involved in this breach and hard to change

What Eskenazi Health has done so far

Only actions the company has announced or that are documented in the sources below. If something you'd expect to see isn't here, it hasn't been announced as of the last update.

Sources

Primary sources first: company disclosures, regulator and attorney general filings, SEC filings, court documents. News reporting is listed as secondary. Where reports conflict, the conflict is noted in the "What happened" section rather than resolved silently.

Primary 01
Eskenazi Health · September 25, 2026

Last updated September 26, 2026 · First published September 26, 2026

Questions about the Eskenazi Health breach

Eskenazi Health (Indianapolis), a public hospital division of the Health & Hospital Corporation of Marion County (HHC), posted a Notice of Data Security Incident on September 25, 2026.

The company has not disclosed how many people were affected. Company notice does not state a headcount.

Unauthorized access is reported to have occurred June 3, 2026 – July 27, 2026 (unauthorized access window).

The company says it discovered the breach on July 27, 2026. It disclosed the incident publicly on September 25, 2026 (company incident notice posted).

The company has not confirmed which categories were exposed. See the full list with status labels above.

The most reliable way is a notice from Eskenazi Health itself. Letters to impacted individuals with identity-protection enrollment instructions. Be cautious of unsolicited messages claiming to confirm you were affected; verify through a contact method you already have.

Start with the checklist above: follow the company's instructions, watch for phishing that references the breach, monitor the affected accounts, and consider a credit freeze if identifiers like a Social Security number are confirmed involved.

Letters to impacted individuals with identity-protection enrollment instructions.

Yes. Information that can't be changed, such as a name, date of birth, or Social Security number, can remain useful for fraud attempts long after the incident. That is a general risk, not a statement that data from this breach has been used.

AI Protection is an identity protection service that includes identity monitoring, removal of exposed information, restoration support, up to $5m identity theft insurance, social media monitoring. It is independent of Eskenazi Health and cannot reverse a breach.

Take control of what happens next.

Monitoring for misuse of your information, removal of what else is out there, and a real person to call if something goes wrong. Plans from $7 per month. Cancel anytime.