DataBreaches.Net

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

Proliance Surgeons notifying 437,392 patients after ransomware attack earlier this year

Posted on November 30, 2023 by Dissent

On November 17, Proliance Surgeons notified HHS that 437,392 patients were affected by a breach. An undated notice on their website explains that it was a ransomware attack in which files and systems were encrypted and some data was exfiltrated.

“After a thorough forensic investigation, we discovered on May 24, 2023, that additional files may have contained personal information, and may have been accessed by an unauthorized party on or around February 11, 2023, however, we had not yet identified the specific individuals involved. We subsequently conducted a detailed and comprehensive review of all the data involved, identified the specific individuals whose information may have been accessed or acquired, and took steps to immediately notify potentially affected individuals of the incident. The information involved includes individual names, and one or more of the following: date of birth, Social Security number, medical treatment information, health insurance information, phone number, email address, financial account number, driver license or other identification information, and usernames and passwords. We are notifying affected individuals about the incident via letter,” they wrote.

Their full notification can be found on their website. Unfortunately, it leaves a number of questions unanswered.

DataBreaches sent an email to Proliance Surgeons with the following preliminary questions:

1. When did the attack occur?
2. When did Proliance first discover that it was the victim of a cyberattack?
3. Did Proliance have current and usable backups to restore from?
4. Did Proliance negotiate with, or interact with, the threat actors at all?
5. What group or threat actor was responsible for this attack?
6. Has any data from this attack shown up on the dark web or clear net?

No reply has been received as yet, but DataBreaches will update this post when a reply is received. Proliance Surgeons are independent specialists and surgeons who own their own centers. There are more than 400 providers and more than 100 locations in the Washington area. Their notification does not indicate that only one center or so was affected, so it seems like there is a central network for all locations, which raises other questions.

As far as DataBreaches could determine, this incident has not shown up on any of the dark web ransomware leak sites. If the incident was in February or earlier, that could indicate that Proliance had paid the attackers, but there are other possible explanations and it would be best if Proliance issued an unequivocally clear statement about whether they paid ransom or not.

 


Related:

  • 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
  • John Bolton Indictment Provides Interesting Details About Hack of His AOL Account and Extortion Attempt
  • UK: 'Catastrophic' attack as Russians hack files on EIGHT MoD bases and post them on the dark web
Category: Breach IncidentsHealth DataMalwareOf Note

Post navigation

← After $50 Million Breach, KyberSwap Faces Hacker’s Shocking Demands
OAIC alleges Australian Clinical Labs hack resulted from lacklustre security measures →

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.