DataBreaches.Net

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

Breach notification letters create second breach for health co-op

Posted on May 1, 2015 by Dissent

I had been a bit critical in reporting on a recent breach involving the Oregon’s Health Co-Op, writing:

In reading the substitute notice below, note that they do not say from where the laptop was stolen, nor how many were affected. And what kind of “commitment” to privacy is it to just password-protect a laptop with PHI – and to keep “former member and dependent” information on it? C’mon, folks. We can and must do better.

But it was not to be this week, it seems.  A reader e-mailed me last night to call my attention to the fact that the Co-Op had a second breach involving the breach notification letters. He wrote:

When sending out letters letting people know what happened, they somehow mixed up customer address with other customers. I did not receive any [notification letters]  on the policies I have at my address (a total of five). Instead I received five letters of other customers…. After calling this seems to be the case with most customers. It give a code number to sign up with protection with that persons name.

Oops? So I checked their site, and sure enough, Oregon’s Health Co-Op now has an FAQ on the breach involving breach notification letters. They write:

I just received a letter from Oregon’s Health CO-OP with someone else’s name. The letter is about a security incident. I am a member of the CO-OP but I am not sure that this is for me.

We apologize for the confusion.  Yes, the CO-OP is notifying members about a recent security incident. If you received a letter with someone else’s name, please destroy that letter. Another letter with correct information is on the way to you.

What happened with the first letter? Why was it incorrect?

There was a system error with the first letter. We identified the root cause, corrected the error and are re-issuing letters with updated personal codes to the entire list of current and former members. We expect these letters to be in the US Postal Mail by Wednesday, May 6.

Why should I trust ID Experts to handle protecting my data when they can’t send out a letter correctly?

I understand your frustration.  The error was not ID Experts; we accept responsibility for the database/mailing list error.  ID Experts has information that is important to you. We encourage you to contact them to register for the protection services we are providing.

Why did I receive multiple letters to people that I don’t know?

Everyone who is impacted by this security incident has been notified.  This includes all family members, which is why some households received multiple letters.

And no, we still don’t know how many people had information on the stolen laptop or where it was stolen. Oregon news outlets reporting on the breach seem to have stuck to the co-op’s press release and not asked any questions.

 


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.
  • Data breach in 42 Latvian municipalities: DVI imposes 300,000 euro fine on ZZ Dats
  • Kaufman County's data breach was their second one in three weeks
  • Protected health information of 462,000 members of Blue Cross Blue Shield of Montana involved in Conduent data breach
  • TX: Kaufman County Faces Cybersecurity Attack: Courthouse Computer Operations Disrupted
Category: ExposureGovernment SectorHealth DataPaperU.S.

Post navigation

← UK: Dumfries and Galloway Council data breach actions accepted
Macedonian prosecutor indicts opposition leader in wiretap scandal →

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

  • 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
  • A jailed hacking kingpin reveals all about the gang that left a trail of destruction
  • Army gynecologist took secret videos of patients during intimate exams, lawsuit says
  • The Case for Making EdTech Companies Liable Under FERPA
  • NHS providers reviewing stolen Synnovis data published by cyber criminals

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

  • 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
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation
  • Who’s watching the watchers? This Mozilla fellow, and her Surveillance Watch map

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.