DataBreaches.Net

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

Judge Denies Yahoo Privacy Data Breach Settlement

Posted on January 29, 2019 by Dissent

Matthew Renda reports:

A federal judge denied approval of a settlement in the Yahoo data breach class action on Monday, saying Yahoo’s refusal to disclose the total amount to be paid out to those affected by the largest data breach in history renders it insufficient.

“The proposed notice does not disclose the costs of credit monitoring services or costs for class notice and settlement administration, and does not disclose the total size of the settlement fund,” U.S. District Judge Lucy Koh wrote in a 24-page ruling. “Without knowing the total size of the settlement fund, class members cannot assess the reasonableness of the settlement.”

Koh’s denial of the settlement comes as no surprise to those who followed the case closely, as the judge badgered both sides with questions during a November hearing and expressed displeasure particularly aimed at the plaintiffs, who she accused of being more concerned about getting paid than investigating how Yahoo allowed hackers gain access to the private data of its customers.

Read more on Courthouse News.

h/t, Joe Cadillic


Related:

  • Another plastic surgery practice fell prey to a cyberattack that acquired patient photos and info
  • How a hacking gang held Italy’s political elites to ransom
  • NY: Gloversville hit by ransomware attack, paid ransom
  • UN Cybercrime Convention to be signed in Hanoi to tackle global offences
  • 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.
Category: Business SectorHackOf NoteU.S.

Post navigation

← B&Q ‘exposed data about store thieves’
China most active in cyber espionage against U.S.: Coats →

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.