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:

  • Resource: NY DFS Issues New Cybersecurity Guidance to Address Risks Associated with the Use of Third-Party Service Providers
  • TX: Kaufman County Faces Cybersecurity Attack: Courthouse Computer Operations Disrupted
  • Bombay High Court Orders Department of Telecommunications to Block Medusa Accounts After Generali Insurance Data Breach
  • 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
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

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