DataBreaches.Net

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

UT: EMI Health alerting plan members to breach — notices will follow at a later date

Posted on October 23, 2021 by Dissent

EMI Health is committed to protecting the confidentiality and security of our members’ information. Regrettably, we recently identified and addressed a security incident that involved some of our members’ information.

On August 10, 2021, we identified unusual network activity. We immediately took steps to secure the network and began an investigation with the assistance of a computer forensic firm. The investigation determined that an unauthorized person gained access to our network between July 29, 2021 and August 10, 2021 and deployed malware on our systems. On August 23, 2021, we determined that the unauthorized person acquired copies of some documents from our systems that contained member information. We immediately began a comprehensive review of all documents involved. The review is ongoing, and we do not yet know which specific members’ information was involved. However, we believe that the documents contain one or more of the following related to some of our members: names, Social Security numbers, driver’s license numbers, addresses, dates of birth, health insurance identification numbers, and/or clinical information, such as diagnosis and treatment information. At this time, we do not believe that members’ full financial account numbers were contained in the documents involved.

Once the review is complete, EMI Health will mail letters to members whose information is identified in the documents. We have established a dedicated, toll-free call center to answer members’ questions. If you have questions, please call 1-855-675-3110, Monday through Friday, from 7:00 a.m. to 7:00 p.m., Mountain Time. For those members whose Social Security numbers and/or driver’s license numbers are identified in the documents, EMI Health will offer complimentary credit monitoring and identity protection services, enrollment instructions for which will be contained in the notification letters to be sent as soon as possible. We are conducting an extra level of review of claims submitted to help identify fraudulent claims. It is also recommended that affected members review any statements they receive from EMI Health and their healthcare providers. If members see charges for services not received, they should contact our customer service department at 1-800-662-5851 or [email protected] or the healthcare provider immediately.

We regret any concern or inconvenience this incident may cause. We remain committed to protecting the confidentiality and security of member information. To help prevent something like this from happening again, we are continuing to regularly audit our system for potential unauthorized activity and are implementing enhanced network monitoring tools.

Source: EMI Health

h/t, ABC4 who first reported this story.


Related:

  • TX: Kaufman County Faces Cybersecurity Attack: Courthouse Computer Operations Disrupted
  • Attorney General James Announces Settlement with Wojeski & Company Accounting Firm
  • JFL Lost Up to $800,000 Weekly After Cyberattack, CEO Says No Patient or Staff Data Was Compromised
  • Before Their Telegram Channel Was Banned Again, ScatteredLAPSUS$Hunters Dropped Files Doxing Government Employees (2)
  • Massachusetts hospitals Heywood, Athol say outage was a cybersecurity incident
  • Data BreachesProsper Data Breach Impacts 17.6 Million Accounts
Category: Health DataU.S.

Post navigation

← TX: Unable to determine what was accessed in cyberattack, McAllen Surgical Specialty Center, Ltd. is notifying patients as well as employees
Under attack by “Groove,” TriValley Primary Care posts notice on web site and continues caring for patients →

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

  • 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
  • The Case for Making EdTech Companies Liable Under FERPA
  • NHS providers reviewing stolen Synnovis data published by cyber criminals

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

  • 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
  • Who’s watching the watchers? This Mozilla fellow, and her Surveillance Watch map

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.