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.

 

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

  • Banks Want SEC to Rescind Cyberattack Disclosure Requirements
  • MathWorks, Creator of MATLAB, Confirms Ransomware Attack
  • Russian hospital programmer gets 14 years for leaking soldier data to Ukraine
  • MSCS board renews contract with PowerSchool while suing them
  • Iranian Man Pleaded Guilty to Role in Robbinhood Ransomware
  • Developments surrounding data breach at Dutch police
  • Estonia launches international search for Moroccan citizen wanted over data theft
  • Now it’s Tiffany: Another LVMH luxury brand hit by hackers
  • Dutch Government: More forms of espionage to be a criminal offence from 15 May onwards
  • B.C. health authority faces class-action lawsuit over 2009 data breach (1)

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

  • The CCPA emerges as a new legal battleground for web tracking litigation
  • U.S. Spy Agencies Are Getting a One-Stop Shop to Buy Your Most Sensitive Personal Data
  • Period Tracking App Users Win Class Status in Google, Meta Suit
  • AI: the Italian Supervisory Authority fines Luka, the U.S. company behind chatbot “Replika,” 5 Million €
  • D.C. Federal Court Rules Termination of Democrat PCLOB Members Is Unlawful
  • Meta may continue to train AI with user data, German court says
  • Widow of slain Saudi journalist can’t pursue surveillance claims against Israeli spyware firm

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[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.