DataBreaches.Net

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

Refuah Health Center “recently discovered” a breach that was listed on the dark web in June, 2021?

Posted on May 12, 2022 by Dissent

On April 29, 2022, Refuah Health Center in New York issued a statement on their website that begins:

The privacy and security of the personal and protected health information we maintain is of the utmost importance to Refuah Health Center.

We recently discovered unauthorized access to our network occurred between May 31, 2021 and June 1, 2021.

They “recently” discovered?  Let’s stop right there.

On June 11, 2021, Lorenz ransomware threat actors added the Refuah Health Center to their leak site. How did Refuah only “recently” discover this when it was on a dark web site as early as June 11?  If they had even googled their name, they would likely have come across mentions that Lorenz threat actors had added them to their leak site. HackNotice had noted it and RansomAlert on Twitter had mentioned it.

Lorenz just added a new post: “Refuah Health” #Lorenz #Ransomware #RansomAlert

— RansomAlert (@RansomAlert) June 11, 2021

DataBreaches had also spotted the listing but because Refuah had no contact information on their site other than phone, this site did not reach out to them at the time. The Refuah listing is no longer on Lorenz’s leak site. Refuah’s notice does not mention any ransom demand at all. So exactly what happened here? Are we to believe that Lorenz never tried to extort Refuah? Or that they tried but Refuah ignored their emails or contacts? Were any files encrypted? What exactly happened here that Refuah claims it only recently discovered a breach almost one year old?

Refuah notes that their investigation revealed that “a limited amount of personal and/or protected health information was removed from our network in connection with this incident.”

What do they mean by “limited amount?” This incident was reported to HHS as impacting 260,740 patients, and

The information included the affected individuals’ full names and one or more of the following: Social Security numbers, driver’s license numbers, state identification numbers, dates of birth, bank/financial account information, credit/debit card information, medical treatment/diagnosis information, Medicare/Medicaid numbers (which may be identical to Social Security numbers), medical record numbers, patient account numbers, and/or health insurance policy numbers.

“To date,” they write, “we are not aware of any reports of identity fraud or improper use of any information as a direct result of this incident.”

So what do they think Lorenz did with all that PII and PHI?  Just tuck it away? Did they sell it to others? Is it on a marketplace somewhere? And if Refuah wasn’t aware of the breach for almost one year after it was listed on the dark web, can we have any faith in their report that they are not aware of any identity fraud or improper use?

You can read their full notice on their website.

DataBreaches has sent an inquiry to Lorenz yesterday to see if we can get more information about what happened in this incident, and will update this post if a response is received.

 

Related posts:

  • Attorney General James Reaches Agreement with Refuah Health Center to Invest $1.2 Million to Protect Patient Data and Pay $450,000 in Penalties to State
  • HC3 Alert on Lorenz Ransomware
  • Updating: CaptureRx incident impacted more than 2.4 million. List of Entities.
  • Pysa shuttered its leak site before it ever dumped data from more than half a dozen schools. Here’s what we know so far.
Category: Breach IncidentsHealth DataMalware

Post navigation

← DEA Investigating Breach of Law Enforcement Data Portal
Anonymous Social Media App Yik Yak Exposed Users’ Precise Locations →

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

  • Texas Centers for Infectious Disease Associates Notifies Individuals of Data Breach in 2024
  • Battlefords Union Hospitals notifies patients of employee snooping in their records
  • Alert: Scattered Spider has added North American airline and transportation organizations to their target list
  • Northern Light Health patients affected by security incident at Compumedics; 10 healthcare entities affected
  • Privacy commissioner reviewing reported Ontario Health atHome data breach
  • CMS warns Medicare providers of fraud scheme
  • Ex-student charged with wave of cyber attacks on Sydney uni
  • Detaining Hackers Before the Crime? Tamil Nadu’s Supreme Court Approves Preventive Custody for Cyber Offenders
  • Potential Cyberattack Scrambles Columbia University Computer Systems
  • 222,000 customer records allegedly from Manhattan Parking Group leaked

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

  • Germany Wants Apple, Google to Remove DeepSeek From Their App Stores
  • Supreme Court upholds Texas law requiring age verification on porn sites
  • Justices nix Medicaid ‘right’ to choose doctor, defunding Planned Parenthood in South Carolina
  • European Commission publishes its plan to enable more effective law enforcement access to data
  • Sacred Secrets: The Biblical Case for Privacy and Data Protection
  • Microsoft’s Departing Privacy Chief Calls for Regulator Outreach
  • Nestle USA Settles Suit Over Job-Application Medical Questions

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.