DataBreaches.Net

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

Alameda Health System’s second breach went undetected by investigators of first breach?

Posted on July 1, 2022 by Dissent

On June 24, Alameda Health System in California submitted a notification to the California Attorney General’s Office. The notification concerned a breach of an employee’s email account breach that began on April 30, 2020. The breach wasn’t discovered until February 23, 2022, and the account was locked down after that in March.

According to Alameda’s notification, the types of information involved varied by individual but included: name, date of birth, patient ID, clinical or treatment information, health insurance or claims information, Social Security number, and driver’s license number.

But it is not clear to DataBreaches whether Alameda had just forgotten to notify California or if something else happened, because in May, Alameda had already notified HHS of that incident, and had reported that 90,000 patients had been affected.

Earlier Incident

The June 2022 notification appears to be unrelated to a September 2020 notification by Alameda in which they also reported compromise of an employee’s email account. In that earlier case, Alameda reported that on June 17, 2020, they learned that, “for a brief period of time on April 8, 2020, an unauthorized person from outside AHS was able to remotely access the email account of an AHS employee.”  They then “launched an investigation and engaged a leading forensic security firm to assist in our investigation.”

So a leading forensic firm and investigation never detected that another employee email account had been compromised on April 30 or May 1 — just weeks after the known April 8 compromise — and was still compromised at all times during their investigation?

The April 8, 2020 incident reportedly impacted 2,691 patients.

NOTE: DataBreaches.net has seen some sites claiming that the 90,000 breach occurred on April 8 and was discovered June 17 of 2020. No. There were two different breach incidents reported by Alameda Health System.

AHS had two breaches that started within weeks of each other. Both involved employee email accounts.

Related:

  • Two U.K. teenagers appear in court over Transport of London cyber attack
  • ModMed revealed they were victims of a cyberattack in July. Then some data showed up for sale.
  • Toys “R” Us Canada customers notified of breach of personal information
  • Confidence in ransomware recovery is high but actual success rates remain low
  • Kaufman County's data breach was their second one in three weeks
  • Hacking Formula 1: Accessing Max Verstappen's passport and PII through FIA bugs
Category: Breach IncidentsCommentaries and AnalysesHackHealth DataU.S.

Post navigation

← Updating: Breach reports from Eye Care Leaders’ clients continue to add up
Professional Finance Company, Inc. is providing breach notifications to patients of 657 covered entities →

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

  • Suspected Russian hacker reportedly detained in Thailand, faces possible US extradition
  • Did you hear the one about the ransom victim who made a ransom installment payment after they were told that it wouldn’t be accepted?
  • District of Massachusetts Allows Higher-Ed Student Data Breach Claims to Survive
  • End of the game for cybercrime infrastructure: 1025 servers taken down
  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs

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

  • Lawmakers Warn Governors About Sharing Drivers’ Data with Federal Government
  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[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.