DataBreaches.Net

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

Two covered entities who discovered breaches last summer first notifying patients

Posted on January 21, 2022 by Dissent

Two breaches that were first reported to HHS in November have now been more fully disclosed. Both of the following breaches were first reported to HHS in November as impacting 500 or 501 patients — entries that this site usually suspects are just “markers” for “we have no idea yet how many were impacted.”

Anne Arundel Medical Center (Maryland, phishing attack)

Zeke Hartner reports:

Luminis Health, the owners of Anne Arundel Medical Center in Maryland, announced Thursday that its email system was accessed by an unauthorized party, and some patient information could have been exposed during the breach.

The health company said it became aware of the breach within its employee email system on Sept. 3, 2021, and took steps to secure the impacted email accounts.

They then hired a computer forensics firm to assist in an investigation into the incident. That investigation found that an unauthorized person accessed employee email accounts between Aug. 26 and Sept. 14.

Read more at WTOP.

Marietta Area Health Care dba Memorial Health System (Ohio, ransomware)

Evan Bevins reports:

Personal information for more than 200,000 people may have been accessible during a cyber attack on Memorial Health System last year, although officials say there is no indication any identity theft or unauthorized use of the data occurred.

Patients from Memorial whose personal health information, Social Security number, account number or date of birth could have been accessed recently received letters notifying them of the situation. The letter says the recipient’s information was present in systems that were accessed by an “unauthorized actor” around July 10 through Aug. 15.

Read more at News & Sentinel.

Not everyone impacted by the Anne Arundel incident has been sent letters yet — and may not get them for weeks — even though the breach was first discovered on September 3.

The Memorial Health breach was first detected in August. The system gives a chronology of its discovery and investigation, but the bottom line is that neither of these entities notified affected patients “no later than 60 calendar days” from when the breaches were discovered.

What is HHS going to do about this repeated problem of notifications taking many months following initial discovery of a breach?  Anne Arundel discovered a problem on September 3. They appear to have stopped the access by September 14. Four months later, some patients still haven’t been notified.

At some point, we should see an update on the number of patients impacted by the Anne Arundel incident. The Memorial Health incident impacted 216,478 patients.

No related posts.

Category: Health DataMalwarePhishingU.S.

Post navigation

← CA: Chico State computer hacker sentenced
IRS Will Soon Require Selfies for Online Access →

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.