Skip to content
cisonews.net

Incident · Substitute notice (organization website)

LHC Group data breach: vishing call led to theft of patient files from a vendor platform, April 2026

Compiled from public records. Updated 2026-11-15. By the cisonews.net Desk.

LHC Group, a national home health and hospice provider, says a threat actor used stolen credentials to take a large volume of patient files from a third-party vendor's platform between April 7 and April 15, 2026. It began on the day LHC learned that an employee may have been the target of a vishing, or voice phishing, call. The files held clinical summaries, treatment plans, diagnosis codes, insurance details and Medicare and Medicaid ID numbers, and in some cases Social Security numbers. Massachusetts recorded 4,812 residents on September 4, 2026. People who get a letter can enroll in two years of IDX monitoring until December 4, 2026.

Entries like this one, in Wednesday’s docket

Wednesdays

Unsubscribe any time.

DateEvent
April 7, 2026LHC learns an employee may have been the victim of a vishing call; unauthorized access begins
April 15, 2026Last day of unauthorized access
July 9, 2026LHC begins confirming the identities of the people affected
September 4, 2026Report to Massachusetts (2026-1506): 4,812 residents
December 4, 2026Last day to enroll in the IDX monitoring

What happened in the LHC Group breach?

The attack went through a vendor, by way of a phone call. LHC says it uses a third-party technology vendor for referral management, care coordination and clinical workflow in its home health services. On April 7, 2026, LHC became aware that an employee may have been the victim of a vishing attack, and the vendor then reported suspicious activity on its platform tied to an LHC user account. LHC says it investigated, secured its systems, worked with the vendor, brought in third-party forensic experts and notified the FBI.

The notice names neither the vendor nor the employee, and it does not say what the caller asked for. The file name of the PDF on LHC's site calls it a "stolen session" notice; the text itself says the threat actor stole credentials.

What information was exposed?

More than in most breach letters, because the files were clinical. The notice lists names, addresses, dates of birth and demographics; Social Security numbers in limited instances; clinical summaries, treatment plans, diagnosis codes, dates of service and provider details; health insurance policy names, numbers and plan information; Medicare and Medicaid ID numbers; and, in limited instances, financial information. Not every element was involved for every person.

RecordResidentsData marked
Massachusetts OCABR, report 2026-15064,812Social Security numbers, medical records

What is LHC offering, and what should patients do?

Two years of credit monitoring and identity protection through IDX, paid for by LHC. The enrollment deadline is December 4, 2026, using the code in the letter at app.idx.us. The call center is 1-866-200-0905, Monday to Friday, 8 a.m. to 8 p.m. Central Time.

Because the files held health and insurance details, the notice asks people to check explanation of benefits statements as well as bank and credit statements, and to contact their plan about any service they did not receive. LHC says it disabled the compromised account and strengthened authentication and monitoring. The social engineering guide compares other incidents where attackers talked their way in, and the vendor and cloud-tenant guide covers breaches that ran through a vendor's platform.

Why did notice take until September?

LHC says that after extensive review and data analysis it began confirming the identities of the people affected on July 9, 2026. The Massachusetts report followed on September 4, 150 days after the access began. The notice delay guide shows the times other health care organizations took from discovery to notice.

How many people were affected?

The notice gives no total. Massachusetts counts 4,812 of its residents. No other state list fetched for this entry gives a count, and the federal health breach list could not be read when this entry was written.

What the documents leave open

  • The name of the vendor and how the stolen credentials worked on its platform.
  • The total number of patients notified.
  • Whether anyone has claimed the files or asked for payment.

How this disclosure's timing compares

LHC Group, Inc. disclosed 150 days after the discovery date its notice gives. Across the 6 other substitute breach notices on cisonews.net that date discovery to the day, the median gap is 168 days.

Other health care incidents on cisonews.net

All health care incidents

Sources

  1. 2026-09-03 · ALHC Group, Inc., substitute notice of data security incident (company website), published September 3, 2026
  2. 2026-11-15 · AMassachusetts Office of Consumer Affairs and Business Regulation, 2026 Data Breach Notification Report (checked November 15, 2026), published November 15, 2026

Tier A: the organization itself (including notices it filed with a state attorney general), a regulator or SEC EDGAR. Tier B: established press. Each fact on this page carries its supporting passage in the page source.

Entries like this one, in Wednesday’s docket

Wednesdays

Unsubscribe any time.