DataBreaches.Net

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

It was all going so well until….. it wasn’t.

Posted on August 28, 2018 by Dissent

So the server you use to share files with clients got infected with ransomware and you paid the attackers to get the decryption key and recover seems to be going pretty well – you’re able to decrypt the data without any impact on the services you provide to clients…. and then, three days later, you realize:

that the attackers were inadvertently provided a file that contained personal information of IBU’s members, including Social Security numbers

Provided with the file ….how? And when? At the time of payment? Either way, this is not the kind of thing I’d want to be reporting to C-Suite or any clients if this was a mistake made during incident response.  If the letter simply means that HMC discovered that one file on the server contained members’ SSN and they reported that to the client, okay, but the wording of the notification raises questions about what happened here.

Read the full notification letter from Health Management Concepts below. ”

health-management--20180823

DataBreaches.net reached out to HMC to request an explanation of how this happened, and whether any patients of any clients had their protected health information encrypted by the ransomware, but received no response. This post will be updated if a response is received.

 

No related posts.

Category: Breach Incidents

Post navigation

← Leaked data from Chinese hotel chain may affect 130 million customers
Fiserv Flaw Exposed Customer Data at Hundreds of Banks →

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

  • DOJ investigates ex-ransomware negotiator over extortion kickbacks
  • Hackers Using PDFs to Impersonate Microsoft, DocuSign, and More in Callback Phishing Campaigns
  • One in Five Law Firms Hit by Cyberattacks Over Past 12 Months
  • U.S. Sanctions Russian Bulletproof Hosting Provider for Supporting Cybercriminals Behind Ransomware
  • Senator Chides FBI for Weak Advice on Mobile Security
  • Cl0p cybercrime gang’s data exfiltration tool found vulnerable to RCE attacks
  • Kelly Benefits updates its 2024 data breach report: impacts 550,000 customers
  • Qantas customers involved in mammoth data breach
  • CMS Sending Letters to 103,000 Medicare beneficiaries whose info was involved in a Medicare.gov breach.
  • Esse Health provides update about April cyberattack and notifies 263,601 people (1)

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

  • Oregon Amends Its Comprehensive Privacy Statute
  • Wisconsin Supreme Court’s Liberal Majority Strikes Down 176-Year-Old Abortion Ban
  • 20 States Sue HHS to Stop Medicaid Data Sharing with ICE
  • Kids are making deepfakes of each other, and laws aren’t keeping up
  • The Trump administration is building a national citizenship data system
  • Supreme Court Decision on Age Verification Tramples Free Speech and Undermines Privacy
  • New Jersey Issues Draft Privacy Regulations: The New

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.