DataBreaches.Net

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

Parathon by JDA e-Health: what we still don’t know about their July ransomware incident

Posted on January 2, 2024 by Dissent

On August 1, DataBreaches noticed that Parathon by JDA e-Health had been listed on the Akira ransomware leak site. Neither Akira nor Parathon responded to DataBreaches’ inquiries at the time, as DataBreaches reported on August 6.

On October 30, Parathon issued a notice of security incident. The notice stated, in part:

On July 27, 2023, Parathon detected that it was the target of a cybersecurity attack. An unauthorized third party attempted to infiltrate Parathon’s computer network and demand a ransom payment.

[…]

As a result of the incident, Parathon determined that the following personal information could have been accessed by an unauthorized third party: name, address, date of birth, and/or protected health information. The types of information affected were different for each individual, and not every individual had all of the above-list elements exposed. Importantly, the potentially exposed information does not include passwords, financial account information such as bank account numbers or credit card numbers, or social security numbers.

While the investigation found no evidence that any information has been specifically misused to date, Parathon today is mailing letters to potentially involved individuals with detail about the incident and providing resources they can use to help protect their information. Parathon is also offering potentially involved individuals access to free credit monitoring and identity theft protection services through Cyberscout, a leading identity protection company.

Its December 22 letter to those affected, a copy of which was submitted to the Montana Attorney General’s Office, also included this sentence:

“We have taken all efforts possible to mitigate any further exposure of your personal information and related identity theft.”

What does “all efforts possible” mean? Does it mean they paid the ransom demand? In checking Akira’s leak site at various times since the beginning of August, DataBreaches noticed that the Parathon listing had been removed at some point.

Parathon is a business associate for numerous HIPAA-covered entities. The December 22 letter they submitted to Montana was on behalf of NorthShore University Health System. That letter does not disclose the number of affected patients for that client nor all affected patients, total. Nor is there any listing on HHS’s public breach tool from Parathon about this incident or from NorthShore University Hospital System.

So how many patients, total, have been affected by this incident that was first detected in July and has still not been fully disclosed five months later? Thousands? Hundreds of thousands? Millions? DataBreaches sent another inquiry to Parathon through their website last week, asking how many patients, total, were affected by the Akira ransomware attack, whether HHS has been notified by them, and whether they paid Akira any ransom.

No reply has been received as yet.


Related:

  • Two more entities have folded after ransomware attacks
  • British institutions to be banned from paying ransoms to Russian hackers
  • Data breach feared after cyberattack on AMEOS hospitals in Germany
  • Microsoft Releases Urgent Patch for SharePoint RCE Flaw Exploited in Ongoing Cyber Attacks
  • Global hack on Microsoft product hits U.S., state agencies, researchers say
  • Michigan ‘ATM jackpotting’: Florida men allegedly forced machines to dispense $107K
Category: Breach IncidentsCommentaries and AnalysesHealth DataMalwareOf NoteU.S.

Post navigation

← Russian hackers believed to be behind cyber attack on Victoria’s County Court
Operation Triangulation: The last (hardware) mystery →

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

  • BlackSuit ransomware site seized as part of Operation Checkmate
  • The day after XSS.is forum was seized, it struggles to come back online — but is it really them?
  • U.S. nuclear and health agencies hit in Microsoft SharePoint breach
  • Russia suspected of hacking Dutch prosecution service systems
  • Korea imposes 343 million won penalty on HAESUNG DS for data breach of 70,000 shareholders
  • Paying cyberattackers is wrong, right? Should Taos County’s incident be an exception? (1)
  • HHS OCR Settles HIPAA Ransomware Investigation with Syracuse ASC for $250k plus corrective action plan
  • IVF provider Genea notifies patients about the cyberattack earlier this year.
  • Key figure behind major Russian-speaking cybercrime forum targeted in Ukraine
  • Clorox Files $380M Suit Alleging Cognizant Gave Hackers Passwords in Catastrophic 2023 Cyberattack

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

  • Indonesia asked to reassess data privacy terms in new U.S. trade deal
  • Meta Denies Tracking Menstrual Data in Flo Health Privacy Trial
  • Wikipedia seeks to shield contributors from UK law targeting online anonymity
  • British government reportedlu set to back down on secret iCloud backdoor after US pressure
  • Idaho agrees not to prosecute doctors for out-of-state abortion referrals
  • As companies race to add AI, terms of service changes are going to freak a lot of people out. Think twice before granting consent!
  • Uganda orders Google to register as a data-controller within 30 days after landmark privacy ruling

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.