DataBreaches.Net

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

How many clients and patients were affected by a ransomware attack on EqualizeRCM? We have no idea.

Posted on July 2, 2024 by Dissent

On August 17, 2023, SysInformation Healthcare Services, LLC, d/b/a EqualizeRCM (“SysInformation”) notified HHS of a breach. The firm, a business associate that provides revenue and billing cycle management services, reported that 501 patients had been affected. That number is generally interpreted as a placeholder marker when the entity has not yet figured out the real number affected. In Protenus’s annual Breach Barometer report, the SysInformation breach was one of the more than 50 entities with a marker that had not been updated by the end of 2023.

In April 2024, SysInformation notified the Vermont Attorney General of the breach and provided a template notification letter. The template letter appears to have been sent on behalf of an unnamed client. The letter explained that an attack had occurred between June 3 and June 18, 2023, and abnormal activity was detected on June 18. SysInformation did not explain whether this was a ransomware attack or some other type of incident but did state that patient data had been accessed or acquired.

The April 26, 2024 letter did not explain why SysInformation took from June 2023 until the end of April 2024 to notify those affected. A check of HHS’s breach site shows that as of the April 26, 2024 letter, SysInformation still had not updated its report to HHS regarding the number of patients affected.

On July 1, 2024, SysInformation issued a press release on behalf of one of their clients, Atlanta Perinatal Consultants, LLP, d/b/a Georgia Perinatal Consultants (“GPC”). The press release contains much of the same information as in the April 26 letter template, but the press release specifically mentioned that this was a ransomware attack.

The press release also states that GPC was notified of the breach on May 6, 2024. Did SysInformation notify GPC at all prior to May 6, 2024?

Although the information varied by individual, the information of affected GPC individuals was reported to potentially include name, date of birth, health insurance information, medical history/treatment information, and in very few cases Social Security number, email address, and telephone or fax numbers. SysInformation has reported that there is no evidence to indicate that any GPC patient’s driver’s license number, financial account information, or address information was compromised.

The notification to HHS still hasn’t been updated, so we do not know the total number of patients affected or what clients other than GPC have been affected by the incident.

DataBreaches is not aware of any group claiming responsibility for this particular attack or leaking it on any site.


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
  • A business's cyber insurance policy included ransom coverage, but when they needed it, the insurer refused to pay. Why?
  • Before Their Telegram Channel Was Banned Again, ScatteredLAPSUS$Hunters Dropped Files Doxing Government Employees (2)
Category: Breach IncidentsHealth DataMalwareSubcontractorU.S.

Post navigation

← “Sadly for the feds I have not been arrested” – RansomedVC
HHS Office for Civil Rights Settles HIPAA Security Rule Failures for $950,000 →

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

  • 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
  • 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

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

  • 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
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation

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.