DataBreaches.Net

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

Four months after learning of a vendor’s breach, Concord Orthopaedics notifies almost 68,000 patients (1)

Posted on March 27, 2025March 27, 2025 by Dissent

In November 2024, Everest Team added Concord Orthopaedics (“COPA”) to its dark web leak site (DLS) with screenshots offered as proof of claims. At the time, Everest claimed to have acquired “medical records and personal data of all patients from 2018. More than 30,000 identity documents.”

On March 25, 2025, COPA mailed notifications to those affected, and their counsel notified the New Hampshire Attorney General’s Office about the incident.

According to their notification, on November 21, 2024,COPA learned that a vendor who handles their patient registration and appointment check-in software was breached. They do not name the vendor but say that COPA’s own internal environment was not affected at all. The types of information accessed or acquired from the vendor’s software included:

  • Name
  • Date of birth
  • Social Security number
  • Appointment Information: The information captured by the third-party software is limited to information related to the appointment, such as appointment type (for example, surgical, MRI, etc.), treating physician name, and date and location of appointment
  • Health Insurance Information: This may include health plan beneficiary number, health plan number, and insurance eligibility information. Some of this information may belong to the primary insurance holder.
  • Driver’s License or State Identification Number: For a portion of the population, an image of your driver’s license or state identification card may be impacted.

On January 28, 2025, the third-party vendor provided COPA with the data potentially impacted.

According to the notification to New Hampshire by Troutman Pepper Locke, 67,835 New Hampshire residents were affected by the incident. The total number of patients was not reported, and as of publication, no listing has shown up on HHS’s public breach tool for incidents affecting more than 500 patients.

But as COPA announced it was mailing out letters, Everest was announcing that it had leaked the data from COPA. The data tranche was 2.9 GB of files.

Update 1: This incident was also reported to the Massachusetts Attorney General’s Office as affecting 1,517 Massachusetts residents.

Everest made data from the Concord Orthopaedics data breach freely available to forum members. The listing claimed to have data on more than 30,000 patients from 2018.

Everest’s description of the data tranche was somewhat incomplete. DataBreaches did find one file with more than 30,000 images of driver’s licenses, but there were other files in .csv format with a wealth of personal and protected health information on patients seen between 2019-2024. This leak involved much more than patients seen in 2018.

Why the unnamed vendor stored so much unencrypted PII and PHI on their server is unknown to DataBreaches.


Related:

  • Massachusetts hospitals Heywood, Athol say outage was a cybersecurity incident
  • Heritage Provider Network $49.99M Class Action Settlement
  • Integris Health Agrees to $30 Million Settlement Over 2023 Data Breach
  • They were victims of a massive data breach in 2009. Interior Health denied it for a decade.
  • Watsonville Community Hospital had a data breach -- or two. It would be helpful to know which.
  • Missing Risk Analysis Cost NY CPA Firm $175K—But Not the Big Group Whose Data Was Breached in 2019
Category: Health Data

Post navigation

← Blacklock Ransomware: A Late Holiday Gift with Intrusion into the Threat Actor’s Infrastructure
Canadian citizen allegedly involved in Snowflake attacks consents to extradition to US →

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.