DataBreaches.Net

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

Less than two weeks after an Indiana hospital reported a phishing-related HIPAA breach, they had a second one

Posted on April 11, 2020 by Dissent

I was working today on adding details to spreadsheets that I use in calculating the gap between breach and discovery, and between discovery and notification. One of the incidents I was looking into today involved a report from Lafayette Regional Rehabilitation Hospital in Indiana. On November 25, they learned that in July, 2019 someone had been accessing emails with patient information after an employee’s email account was compromised. On January 24 of this year, they made notifications to 1,360 patients.

But in getting the details of that incident from their website, I saw that they linked to a second notification. I opened it, thinking it might be an update to their first notification. It wasn’t.

It turns out that less than two weeks after notifying patients of the first incident, the hospital had a second, and seemingly identical, breach.

This second notification stated:

On February 10, 2020, we determined that there may have been unauthorized access to one of our employee’s email accounts that contained patient information between February 3, 2020 and February 8, 2020.

Once again, they were notifying some of their patients that their name, date of birth, and information about the care they received at our facility, had potentially been accessed. In some cases, Social Security numbers were also potentially accessed.

Notifications to an unspecified number of patients began on April 10.

This incident has not yet appeared on HHS’s public breach tool so this site does not yet know how many patients were notified about this one.

On January 24, the hospital noted that in response to the July incident, they were reinforcing training with employees and also working to enhance their security tools.  But it sounds like on February 3, an employee fell for another phishing attack.  Maybe they had not yet received the retraining.

On a positive note, it seems that the hospital detected the second breach much faster than the first one.

 


Related:

  • Two U.K. teenagers appear in court over Transport of London cyber attack
  • 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
  • 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
Category: Breach IncidentsHealth DataPhishing

Post navigation

← A business associate’s response to a breach raises questions of timeliness
New Wiper Malware impersonates security researchers as prank →

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.