DataBreaches.Net

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

ME: InterMed, P.A. notifying patients after 4 employees fall for phishing attack

Posted on November 5, 2019 by Dissent

Notice posted on InterMed, P.A.’s web site, Nov. 4:

On September 6, 2019, we learned that an unauthorized individual gained access to an employee’s email account between September 4 and September 6, 2019. We immediately took steps to secure the account, began an internal investigation, and engaged a leading national computer forensic firm to conduct an independent investigation and file review.

The investigation could not determine what specific messages or attachments were viewed — if any — but did determine that three additional email accounts were likely subject to unauthorized access between September 7 and September 10, 2019.

In an abundance of caution, we reviewed the messages and attachments in the email accounts to identify patients whose information may have been accessible to the unauthorized individual. The review of the email accounts determined that they contained some patient information, which may have included patient names, dates of birth, health insurance information, and/or clinical information. Social Security numbers belonging to a very limited number of patients were also found in the accounts. This incident did not involve InterMed’s electronic health record application, and did not impact all InterMed patients – only those patients whose information was in the affected email accounts. Although our investigation is ongoing, we will begin mailing notification letters on November 5, 2019. We are working quickly to identify and notify all patients whose information was in the accounts.

We deeply regret any concern this may cause. The health and safety of our patients — including the safety of patient data — is our top priority. To help prevent something like this from happening again, we are enhancing our adherence to email best practices.

We have established a dedicated, toll-free call center to answer any questions individuals may have about the incident. Patients with questions can call the call center at 1-855-946-0129, Monday through Friday, between 9:00 a.m. and 6:30 p.m. Eastern Time. For those patients whose Social Security number was contained in the email accounts, we are offering complimentary credit monitoring and identity protection services. We also recommend that affected patients review statements they receive from their health insurers or healthcare providers. If they see charges for services not received, they should contact the insurer or provider immediately.


Related: NBC News reports that 30,000 patients are being notified.


Related:

  • ModMed revealed they were victims of a cyberattack in July. Then some data showed up for sale.
  • KT Chief to Resign After Cybersecurity Breach Resolution
  • Cyber-Attack On Bectu’s Parent Union Sparks UK National Security Concerns
  • A business's cyber insurance policy included ransom coverage, but when they needed it, the insurer refused to pay. Why?
  • Before Their Telegram Channel Was Banned Again, ScatteredLAPSUS$Hunters Dropped Files Doxing Government Employees (2)
  • Attorney General James Secures $14.2 Million from Car Insurance Companies Over Data Breaches
Category: Breach Incidents

Post navigation

← Now available: Catalan Information Security Center produces reports in English for the 2019 Barcelona Congress
Failure to Encrypt Mobile Devices Leads to $3 Million HIPAA Settlement →

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

  • Suspected Russian hacker reportedly detained in Thailand, faces possible US extradition
  • Did you hear the one about the ransom victim who made a ransom installment payment after they were told that it wouldn’t be accepted?
  • 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

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

  • Lawmakers Warn Governors About Sharing Drivers’ Data with Federal Government
  • 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

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.