DataBreaches.Net

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

Vendor ransomware attack by Ryuk impacted 21 healthcare entities in 2019

Posted on January 20, 2021 by Dissent

A recent report headlining that 560 healthcare facilities were impacted by ransomware attacks in 2020 may have seemed shocking until you realize any one ransomware attack can impact multiple hospitals or clinics in a network (just think of the Universal Health Services incident where the Pennsylvania-based system took 400 facilities offline when they were attacked).  In their article, Emisoft had reported that there were 80 ransomware incidents that had impacted at least 560 facilities.

There’s another example in the news this week:  a third-party mailing service, Metro Presort, was hit with Ryuk ransomware in May, 2019. Metro refused to pay the ransom demand. At the time of the attack, they were currently servicing 21 healthcare entities, providing mailings, invoices, and other services. So some people had their name, address, and health identification compromised.

One of the impacted clients was Salem Clinic, who had 20,928 patients impacted. Another entity was Oregon Heart Center, who had 3,172 people impacted.

We did not hear about that report in 2019, though. Nor in 2020, it seems. It was just in the news this week with a statement that in December, OCR had ruled that no violation of HIPAA had occurred, and that it was closing its investigation. But were these reports ever on HHS’s public breach tool? When was HHS actually notified? When were patients notified?

You can read Virginia Barreda’s report on Salem Statesman Journal.

Category: Health DataMalwareU.S.

Post navigation

← Ucar reveals cyberattack earlier this year
An Overview of Cybersecurity Law in Taiwan →

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

  • Ireland’s Data Protection Commission publishes 2024 Annual Report
  • The headlines suggested Freedman Healthcare suffered a ransomware attack that affected patient data. The reality was quite different.
  • Runsafe report: Medical device cyberattacks threaten patient care, strain budgets, top concern for healthcare sector
  • Ryuk ransomware’s initial access expert extradited to the U.S. from Ukraine
  • Alleged Geisinger hacker will defend himself pro se.
  • Tallahassee Memorial Healthcare reveals it was also impacted by Cerner/Legacy Oracle cyberattack
  • Hospital cyberattack investigation complete, no formal review needed (1)
  • Largest Ever Seizure of Funds Related to Crypto Confidence Scams
  • IMPACT: 170 patients harmed as a result of Qilin’s ransomware attack on NHS vendor Synnovis
  • DOJ’s Data Security Program: Key Compliance Considerations for Impacted Entities

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 Judge Invalidates Biden Rule Protecting Privacy for Abortions
  • DOJ’s Data Security Program: Key Compliance Considerations for Impacted Entities
  • 23andMe fined £2.31 million for failing to protect UK users’ genetic data
  • DOJ Seeks More Time on Tower Dumps
  • Your household smart products must respect your privacy – including your air fryer
  • Vermont signs Kids Code into law, faces legal challenges
  • Data Categories and Surveillance Pricing: Ferguson’s Nuanced Approach to Privacy Innovation

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.