DataBreaches.Net

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

Rocky Mountain Gastroenterology appears to have been attacked by three different groups; more than 169,000 patients affected (1)

Posted on October 21, 2024November 29, 2024 by Dissent

Update: On November 13, Rocky Mountain Gastroenterology (RMG) reported the incident to HHS OCR as affecting 366,491 patients. RMG never responded to the inquiries this site submitted to it on October 19 and October 27.

SuspectFile reports:

This article will cover what appears to be a triple cyberattack on the IT systems of Rocky Mountain Gastroenterology (RMG), a medical clinic specializing in gastroenterology with its main office in Lakewood, Colorado, and 26 operational locations. According to information gathered in recent weeks, the attack was carried out by three different cybercriminal groups.

Initial findings suggested that RMG had been targeted by only two groups, Meow Leaks and RansomHub. However, a third group was later identified thanks to a tip from Dissent at DataBreaches.net: the Trinity ransomware group.

As reported on the respective blogs of these three groups in recent days, the total amount of exfiltrated data is not uniform and varies by group:

  • Trinity: 330 GB
  • RansomHub: 200 GB
  • Meow Leaks: over 80 GB

Currently, the Trinity blog no longer lists any of its victims, but we have confirmed two records through ransomfeed.it and ransomlook.io.

Read more at SuspectFile, who saved us all a lot of time and effort by going through the data leaks and writing up details of what he found.

As of today, there is still no substitute notice or statement on the covered entity’s website about any breach, much less multiple breaches. Nor is there any entry on HHS’s public breach tool, although they do not always post notices as soon as they get them.  Although SuspectFile was able to report that protected health information for 169,000 patients was found, because there was no available tranche from Trinity to examine, we do not know the actual total number of unique patients represented in all three incidents.

This situation seems to call for a thorough investigation that considers, in part, how was access gained in each case — were all threat actors using the same access?  Once they first detected access or abnormal activity, what did RMG do to prevent or block further access?  Trinity was the first to publicly list or claim responsibility for an attack on RMG, followed by RansomHub and then Meow Leaks, but is that the actual sequence in which access was gained?

DataBreaches had emailed an inquiry to RMG on October 19 seeking additional details, but no reply has been received as of publication.

Category: Health DataMalwareU.S.

Post navigation

← 2nd Settlement Triggered by 2017 Ransomware Attack Costs WA Practice $100K; ‘Not a Breach’
Justice Department Issues Comprehensive Proposed Rule Addressing National Security Risks Posed to U.S. Sensitive Data →

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

  • 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
  • UK: Legal Aid Agency hit by cyber security incident
  • Public notice for individuals affected by an information security breach in the Social Services, Health Care and Rescue Services Division of Helsinki
  • PowerSchool paid a hacker’s extortion demand, but now school district clients are being extorted anyway (3)
  • Defending Against UNC3944: Cybercrime Hardening Guidance from the Frontlines

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

  • 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
  • Apple Siri Eavesdropping Payout Deadline Confirmed—How To Make A Claim
  • Privacy matters to Canadians – Privacy Commissioner of Canada marks Privacy Awareness Week with release of latest survey results
  • Missouri Clinic Must Give State AG Minor Trans Care Information

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.