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.

Related posts:

  • North Memorial Hospital settles HHS charges for $1.55M
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

  • Alert: Scattered Spider has added North American airline and transportation organizations to their target list
  • Northern Light Health patients affected by security incident at Compumedics; 10 healthcare entities affected
  • Privacy commissioner reviewing reported Ontario Health atHome data breach
  • CMS warns Medicare providers of fraud scheme
  • Ex-student charged with wave of cyber attacks on Sydney uni
  • Detaining Hackers Before the Crime? Tamil Nadu’s Supreme Court Approves Preventive Custody for Cyber Offenders
  • Potential Cyberattack Scrambles Columbia University Computer Systems
  • 222,000 customer records allegedly from Manhattan Parking Group leaked
  • Breaches have consequences (sometimes) (1)
  • Kansas City Man Pleads Guilty for Hacking a Non-Profit

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

  • Germany Wants Apple, Google to Remove DeepSeek From Their App Stores
  • Supreme Court upholds Texas law requiring age verification on porn sites
  • Justices nix Medicaid ‘right’ to choose doctor, defunding Planned Parenthood in South Carolina
  • European Commission publishes its plan to enable more effective law enforcement access to data
  • Sacred Secrets: The Biblical Case for Privacy and Data Protection
  • Microsoft’s Departing Privacy Chief Calls for Regulator Outreach
  • Nestle USA Settles Suit Over Job-Application Medical Questions

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.