DataBreaches.Net

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

Update to Sincera Reproductive Medicine (formerly known as Abington Reproductive Medicine) ransomware incident

Posted on May 18, 2021 by Dissent

On November 8, 2020, in a report called “Without Undue Delay,” DataBreaches.net noted that Maze threat actors had a listing on their dedicated leak site for “Abington Reproductive Medicine.” The proof of claim that they posted, though, was not from Abington Reproductive, leaving us confused as to whether Abington Reproductive had really been a victim or not.  DataBreaches.net had reached out to Abington at the time, but got no responses.

By January 5, 2021, there was still no statement or response to inquiries from Abington (now known as Sincera Reproductive Medicine), and no data from them were dumped by Maze or any other threat actors that appared to collaborate with Maze.

Yesterday, Sincera issued a press release about the incident. It reads, in part:

What Happened?  On September 11, 2020, Sincera observed suspicious activity related to its internal IT systems. In response, Sincera launched an immediate response and investigation of the incident with the assistance of third-party incident response and forensic specialists. Sincera determined that an unauthorized actor had gained access to its systems and Sincera removed that access on September 13, 2020. Additionally, Sincera was able to establish that on August 10, 2020, the unauthorized actor gained access to its systems and may have exfiltrated certain patient data from its network between August 10, 2020 and September 13, 2020.  Sincera subsequently conducted a thorough and comprehensive assessment of information held on its systems that this actor may have had access to and to whom that information pertained.  This included the detailed and labor intensive review of all potentially impacted records which Sincera consolidated and analyzed. On April 22, 2021, Sincera confirmed the specific information potentially impacted during this incident.  While Sincera is unaware of any potential misuse of data related to this incident, they have shared this information with patients in an abundance of caution.

So what…. eight months after discovery, patients were notified?  Given that Maze did not dump the data on their site, it may be that Maze shared or sold the data. And this is why this site keeps reiterating that in the event of a ransomware incident with exfiltration, entities should issue prompt public warnings or notifications to alert patients that their data has possibly been acquiried and may already be on the dark web where criminals acquire data to misuse.

Hopefully, that is not the case with Sincera, but DataBreaches.net repeats its call for HHS to provide some guidance and help on “without undue delay” so that patients are notified not just by 60 days from discovery, but even sooner.

Updated June 3: A potential class action lawsuit was filed in Pennsylvania state court.

Category: Breach IncidentsCommentaries and AnalysesMalware

Post navigation

← NC: Update to Allergy Partners ransomware incident
Student health insurance carrier Guard.me suffers a data breach →

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

  • International cybercrime tackled: Amsterdam police and FBI dismantle proxy service Anyproxy
  • Moldovan Police Arrest Suspect in €4.5M Ransomware Attack on Dutch Research Agency
  • N.W.T.’s medical record system under the microscope after 2 reported cases of snooping
  • Department of Justice says Berkeley Research Group data breach may have exposed information on diocesan sex abuse survivors
  • Masimo Manufacturing Facilities Hit by Cyberattack
  • Education giant Pearson hit by cyberattack exposing customer data
  • Star Health hacker claims sending bullets, threats to top executives: Reports
  • Nova Scotia Power hit by cyberattack, critical infrastructure targeted, no outages reported
  • Georgia hospital defeats data-tracking lawsuit
  • 60K BTC Wallets Tied to LockBit Ransomware Gang 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

  • FTC dismisses privacy concerns in Google breakup
  • ARC sells airline ticket records to ICE and others
  • Clothing Retailer, Todd Snyder, Inc., Settles CPPA Allegations Regarding California Consumer Privacy Act Violations
  • US Customs and Border Protection Plans to Photograph Everyone Exiting the US by Car
  • Google agrees to pay Texas $1.4 billion data privacy settlement
  • The App Store Freedom Act Compromises User Privacy To Punish Big Tech
  • Florida bill requiring encryption backdoors for social media accounts has failed

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.