DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

Monongalia Health System hacked again? Second incident report in one year.

Posted on March 2, 2022 by Dissent

Monongalia Health System in West Virginia issued a press release this week about a data breach that impacted patients, employees, and contractors. It was the second incident reported by them in a one-year period. But was this incident unrelated to the first incident or related to it? It’s not yet clear, let’s back up to their first report and start with that. In December, they had reported that in July, they had discovered that employee email accounts had been compromised by a phishing attack. Mon Health made that discovery when investigating why one of their vendors reported never receiving payment. Their investigation found that unauthorized access to email had occurred between May 10, 2021, and August 15, 2021.

That incident reportedly affected patients and members of Mon Health’s employee health plan: names, Medicare health insurance claim numbers (which could contain Social Security numbers), addresses, dates of birth, patient account numbers, health insurance plan member ID numbers, medical record numbers, dates of service, provider names, claims information, medical and clinical treatment information and/or status as a current or former Mon Health patient. [“Mon Health” refers to Monongalia Health System, Inc., and its affiliated hospitals: Monongalia County General Hospital Company, Stonewall Jackson Memorial Hospital Company, and Preston Memorial Hospital Corporation.]

Mon Health reported to HHS that 398,164 patients were being notified about that incident.

Now the health system has issued a second press release. According to this newest one:

On December 30, 2021, Mon Health determined that a data security incident resulted in unauthorized access to information pertaining to Mon Health patients, providers, employees, and contractors. Mon Health first learned of this incident on December 18, 2021, when it was alerted to unusual activity in its IT network which disrupted the operations of some of Mon Health’s IT systems. The investigation determined that the incident did not involve unauthorized access to Mon Health’s electronic health records systems but unauthorized parties did access its IT network between December 8, 2021, and December 19, 2021. They write:

Mon Health’s investigation cannot rule out the possibility that, while in its IT network, the unauthorized parties may have accessed files on IT systems that contain patient, provider, employee, and contractor information. This information may have included the following information relating to patients and members of Mon Health’s employee health plan: names, addresses, Social Security numbers, Medicare Health Insurance Claim Numbers (which could contain Social Security numbers), dates of birth, patient account numbers, health insurance plan member ID numbers, medical record numbers, dates of service, provider names, claims information, medical and clinical treatment information and/or status as a current or former Mon Health patient or member of Mon Health’s employee health plan.

This is basically the same description as last year’s notification, suggesting that attackers may have hit the same system as last year. And once again, it seems that patient data was not segmented (or not effectively segmented) from employee data and contractor/vendor data.

But was this incident related to last year’s? Did new threat actors exploit the same weakness as previous attackers in a phishing attack that gave them credentials to access the IT system? Did the earlier threat actors leave a backdoor into the system that was now exploited again? Or was this a totally unrelated attack by different threat actors?

So far, Mon Health seems to have escaped a total disaster of having its systems encrypted and patient care significantly disrupted. Hopefully, they will find out exactly how these two incidents occurred so they can harden their security or practices as needed.

This post will be updated when Mon Health responds to this site’s inquiry about whether there is any connection between these incidents.


Related:

  • Another plastic surgery practice fell prey to a cyberattack that acquired patient photos and info
  • How a hacking gang held Italy’s political elites to ransom
  • Uncovering Qilin attack methods exposed through multiple cases
  • Predatory Sparrow Strikes: Coordinated Cyberattacks Seek to Cripple Iran's Critical Infrastructure
  • Ex-CISA head thinks AI might fix code so fast we won't need security teams
  • NY: Gloversville hit by ransomware attack, paid ransom
Category: Breach IncidentsCommentaries and AnalysesHackHealth DataU.S.

Post navigation

← Aon hit by cyber attack
The Tel Aviv company paid millions to stop cyber criminals →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • District of Massachusetts Allows Higher-Ed Student Data Breach Claims to Survive
  • End of the game for cybercrime infrastructure: 1025 servers taken down
  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs
  • A jailed hacking kingpin reveals all about the gang that left a trail of destruction
  • Army gynecologist took secret videos of patients during intimate exams, lawsuit says

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[at]databreaches.net
Mastodon: Infosec.Exchange/@PogoWasRight
Signal: +1 516-776-7756
DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.