The breaches took place approximately six months apart.
What happened
Minnesota Epilepsy Group, P.A. (MEG) recently published a data breach notice on its website, explaining that protected health information may have been accessed after the organization experienced a security incident.
The notice stated MEG discovered an unauthorized third party had accessed its computer network on August 10th, 2026, appearing to have entered and exited on the same day.
Accessed information included names, addresses, dates of birth, Social Security numbers, medical treatment information, and/or health insurance information. The investigation concluded on September 17th, 2026, and the organization began notifying victims on October 14th. According to the Department of Health and Human Services (HHS), the incident impacted 82,574 individuals.
In the know
The Epilepsy group published a separate notice earlier this year, explaining that they had been the victim of a data breach in the spring. This notice explained that they discovered an unauthorized party in their network on April 7th, 2026. An investigation determined that an unknown actor accessed their network between March 16th, 2026, and April 10th, 2026, showing an almost month-long intrusion that was not able to be immediately stopped once detected.
The breach was reported to the HHS as having impacted 80,061 individuals. Data accessed included names, addresses, dates of birth, Social Security numbers, medical treatment information, and/or health insurance information. Victims were sent notices beginning June 5th, 2026.
Why it matters
No group has claimed either breach, so it’s unknown whether the two attacks were carried out by the same threat group. MEG did not share what vulnerability, aside from it being in their computer network, was exploited, meaning that it could have been the same weakness exploited twice, or different vulnerabilities altogether.
Two attacks against a single organization in such a short period of time reveal the frequency of healthcare attacks, and since no group claimed them, it’s possible that they were based on opportunity.
For patients at MEG, they could see themselves potentially being victimized twice, although the same information was involved in both breaches. While having the same information leaked again may not necessarily make an individual more prone to fraud or theft, it could severely weaken patient trust in the healthcare organization. It could also provide additional grounds for legal filing and complaints, both for class action suits and for investigations by the HHS’ Office for Civil Rights or attorneys general. The fact that the second breach only lasted one day shows that MEG may have made some advancements in their response protocol, which potentially limited the amount of data accessed.
The big picture
While it’s not common for an organization to face multiple data breaches, it isn’t unheard of. Many organizations face multiple data breaches over several year periods. For instance, Paubox reported on emergency medical transportation company, Survival Flight, Inc., which faced a data breach in May of 2024 and then another breach in the summer of 2025. Similarly, Paubox reported on how the Radiology Associates of Richmond faced two breaches, one in 2026 (impacting 250,000), and one in 2024 (impacting 1.42 million) that resulted in multiple complaints being filed.
Regardless of why a breach occurred, when multiple instances take place, it’s a clear sign to an organization to step up its cybersecurity practices and simultaneously prepare for legal battles that could span years. For smaller, specialty clinics, like MEG, a single data breach can cause financial repercussions that last year, and a second breach only increases those costs.
FAQs
Is it just a coincidence that MEG was hit with two breaches?
It’s hard to know. Threat actors can be savvy, and if their first attack was successful, it can make them more likely to strike again. This is one of the key reasons it's rarely advised for organizations to pay ransoms, as it can embolden malicious groups to continue their attacks. While it’s possible that this incident was a ransomware attack, it has not been confirmed. Conversely, it’s possible that multiple threat groups saw a weakness in MEG and decided to exploit it.
Does a second attack show that MEG had inadequate cybersecurity?
It’s possible that MEG did not have sufficient cybersecurity systems or is using legacy systems that are difficult to protect. It’s also possible that MEG faced a highly sophisticated attack that was difficult to prepare for. Without full details, it’s hard to know if MEG could have prevented the incident, but organizations should always be looking for ways to strengthen their cybersecurity systems.
