DataBreaches.Net

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

21 months after a ransomware attack, a business associate breach first shows up on HHS’s breach tool. Here’s why.

Posted on March 16, 2021 by Dissent

HIPAA Journal reports on an incident that is illustrative of the challenges entities may face in the wake of a ransomware attack — determining whether a breach is a reportable incident or not. It also illustrates what may happen if an entity decides something is not a reportable breach but further investigation by the U.S. Department of Health & Human Services Office for Civil Rights (OCR) suggests otherwise.

In this case, Metro Presort in Oregon experienced a ransomware attack in May, 2019. They reportedly contained it relatively quickly and recovered from it, reportedly refusing to pay the ransom demanded by Ryuk threat actors. Metro did not report it as a reportable breach under HIPAA because the ePHI on their system was already encrypted (by them) prior to the attack, so the threat actors should not have been able to access any unencrypted ePHI.

Their investigation had found no evidence that any ePHI had been accessed, exfiltrated, or misused. But reinvestigation in October 2020 raised some doubts that  the ePHI had been encrypted before the attack.  In its November 2020 web notice, Metro Presort does not explain why they reinvestigated in October 2020, but an update in that statement suggests that they reinvestigated at OCR’s instigation:

The U.S. Department of Health and Human Services, Office for Civil Rights (“OCR”), which is the federal agency responsible for enforcing the federal health information privacy law known as HIPAA, investigated the incident, MPI’s response, and MPI’s data privacy and security practices. On December 31, 2020, OCR issued a ruling finding no violations of HIPAA and closing its investigation.

HIPAA Journal reports:

The incident has recently appeared on the HHS’ Office for Civil Rights website stating the PHI of up to 38,387 individuals may have been compromised.

But what does that number represent? In January of this year, two of Metro Presort’s clients had disclosed the number of their patients who had been impacted: Salem Clinic reported 20,908 patients were affected, and Oregon Heart Center reported 3,172 patients were impacted. Did Metro Presort’s report to HHS include those approximately 24,000 patients, or is their reported number in addition to them? At the time of the Ryuk ransomware incident, Metro Presort was reportedly providing business associate mailing services to 21 healthcare organizations.

DataBreaches.net sent an inquiry to Metro Presort asking for clarification on the number reported to HHS, i.e., whether it was all inclusive, but has received no reply by the time of this publication. This post will be updated when a reply is received.

Category: Breach IncidentsCommentaries and AnalysesHIPAAMalwareU.S.

Post navigation

← MI: Troy School District website down after hacking from outside U.S., leaders say
The Metropolitan Area of ​​Barcelona hit by ransomware →

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

  • Dublin ETB fined €125,000 for data protection breaches
  • From $5,000 to $800,000: Days Apart, OCR Security Settlements Show Puzzling Math
  • Liberty Township in Ohio has recovered its network after a ransomware attack
  • Marquette County Medical Care Facility discloses data breach
  • Industry Letter – June 23, 2025: Impact to Financial Sector of Ongoing Global Conflicts
  • MNGI Digestive Health settles class action lawsuit stemming from BlackCat attack
  • Four REvil ransomware members released after time served on carding charges
  • Why Dumping Sensitive Data on Network Shares is a Liability
  • A militarily degraded Iran may turn to asymmetrical warfare – raising risk of proxy and cyber attacks
  • Pro-Russian hackers disrupt Dutch government websites ahead of NATO summit

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

  • How Internet of Things devices affect your privacy – even when they’re not yours
  • Sky Views Personal Data as a Potential Weapon in IPTV Piracy War
  • Florida Used a Nationwide Surveillance Camera Network 250 Times To Aid in Immigration Arrests
  • Federal Court Strikes Down HIPAA Reproductive Health Care Privacy Rule
  • The Markup caught 4 more states sharing personal health data with Big Tech
  • Privacy in the Big Sky State: Montana’s Consumer Privacy Law Gets Amended
  • UK Passes Data Use and Access Regulation Bill

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.