DataBreaches.Net

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

A reminder to google your name and email addresses occasionally

Posted on July 28, 2015 by Dissent

In reading news yesterday morning, I stumbled across a question posted on StackExchange:

I found my user details on already old, leaked account information list

I came across an old (>3 years) accounts information list which has been leaked to the web. The list included thousands (>10.000) of account details from a service or services. Apparently the event was a small-scale news item back in the days, so there’s not too much to do now, even if the one page I found would be removed from the web right now.

The query continues, but my immediate reaction was:

Why wasn’t this individual notified of the leak by the entity whose data were leaked?

Yes, we know that there are many leaks like this on a daily basis, and this refers to an incident a while back, it seems, but how many people may still be at risk over old leaks because they were never notified that their email addresses and weakly protected passwords were hacked and dumped? How many of us no longer even remember where we had accounts and where we may have used or re-used certain passwords?

At the very least, people should change their passwords on all current accounts to use stronger passwords or passphrases that are not re-used across sites. Now you, as a savvy reader of this site, know that already, but what about the general public?

And we really need stronger data breach notification laws. Even though we should be diligent in trying to protect ourselves, those who collect and store our information should be obliged to notify us when they have suffered a security failure that exposes our information. It really is as simple as that, and don’t let the business lobby spin it or try to convince you that breach notification fatigue will set in. Yes, maybe people will get tired of getting breach notification letters, but I think we need to let people decide whether to act on a notification or not, and not deprive them of the opportunity to make that decision for themselves.


Related:

  • Inquiry launched after identities of SAS soldiers leaked in fresh data breach
  • Government will 'robustly defend' compensation claims from Afghans put at risk by data breach
  • More than 100 British government personnel exposed by Ministry of Defence data leak
  • North Country Healthcare responds to Stormous's claims of a breach
  • Gladney Adoption Center had serious data exposures in the past few months. What will they do to prevent more?
  • 70% of healthcare cyberattacks result in delayed patient care, report finds
Category: Commentaries and AnalysesExposure

Post navigation

← IM: No action to be taken following email data leak
A Chinese hacking group by any other name? “Black Vine” →

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

  • Scattered Spider Hijacks VMware ESXi to Deploy Ransomware on Critical U.S. Infrastructure
  • Hacker group “Silent Crow” claims responsibility for cyberattack on Russia’s Aeroflot
  • AIIMS ORBO Portal Vulnerability Exposing Sensitive Organ Donor Data Discovered by Researcher
  • Two Data Breaches in Three Years: McKenzie Health
  • Scattered Spider is running a VMware ESXi hacking spree
  • BreachForums — the one that went offline in April — reappears with a new founder/owner
  • Fans React After NASCAR Confirms Ransomware Breach
  • Allianz Life says ‘majority’ of customers’ personal data stolen in cyberattack (1)
  • Infinite Services notifying employees and patients of limited ransomware attack
  • The safe place for women to talk wasn’t so safe: hackers leak 13,000 user photos and IDs from the Tea app

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

  • Congress tries to outlaw AI that jacks up prices based on what it knows about you
  • Microsoft’s controversial Recall feature is now blocked by Brave and AdGuard
  • Trump Administration Issues AI Action Plan and Series of AI Executive Orders
  • Indonesia asked to reassess data privacy terms in new U.S. trade deal
  • Meta Denies Tracking Menstrual Data in Flo Health Privacy Trial
  • Wikipedia seeks to shield contributors from UK law targeting online anonymity
  • British government reportedlu set to back down on secret iCloud backdoor after US pressure

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.