DataBreaches.Net

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

Glassdoor email gaffe exposers users’ email addresses

Posted on July 22, 2016 by Dissent

So Glassdoor updated its terms of service, and dutifully notified its users by putting all their email addresses in the TO: field.  Yeah, you read that right.

And no one apparently noticed before hitting SEND.

Leading to a second email later today:

Dear Glassdoor User:

Earlier today we inadvertently exposed your email address to other
recipients during a routine e-mail distribution regarding changes to our
Terms of Use.

We are extremely sorry for this error. We take the privacy of our users
very seriously and we know this is not what you expect of us. It certainly
isn’t how we intend to operate.

If you have any questions, please contact us at [email protected].

Sincerely,
The Glassdoor Team

Thanks to Jeanne Price for letting me know about this one. I wonder whether anyone hit reply-all as that would have been quite a storm. 🙂

Update: The number affected may be on the order of 600,000.


Related:

  • Des Moines Man Charged with Computer Fraud
  • CrowdStrike catches insider feeding information to ScatteredLapsus$Hunters
  • Fired techie admits sabotaging ex-employer, causing $862K in damage
  • Threat actors have reportedly launched yet another campaign involving an application connected to Salesforce
  • Researchers claim 'largest leak ever' after uncovering WhatsApp enumeration flaw
  • Eurofiber admits crooks swiped data from French unit after cyberattack
Category: Business SectorExposure

Post navigation

← Laser & Dermatologic Surgery Center notifies 31,000 of possible PHI compromise
Wikileaks posts nearly 20,000 hacked DNC emails online →

8 thoughts on “Glassdoor email gaffe exposers users’ email addresses”

  1. Donna says:
    July 25, 2016 at 11:53 am

    So I got won of these apology emails, but what does this breach mean?

    1. Dissent says:
      July 25, 2016 at 1:16 pm

      Not much, actually, except that depending on whether you used a tagged/throwaway email address with them, you might start receiving more spam or phishing attempts.

  2. Javier says:
    July 26, 2016 at 11:54 am

    What a coincidence, that right after I get this message when logging into Glassdoor:

    “We have temporarily disabled your account. We have identified that your password matches one you have used on an unrelated website that has experienced a security breach. Please ​reset your password here.”

    So they screwed with their own security and now try to blame some fictional 3rd party website (how would they know what password I use in that unrelated website? how would they have access to that information? Just tell me which website had that breach, I will decide whether to change my password)

  3. Fulano De Tal says:
    July 28, 2016 at 9:04 pm

    Javier, I got the same message. Seems to me like if they wanted to be helpful they might actually name the “unrelated site” instead of leaving that account wide open.

  4. Anonymous says:
    July 29, 2016 at 9:30 pm

    I also got the email We have temporarily disabled your account. We have identified that your password matches one you have used on an unrelated website that has experienced a security breach. Should I be concerned?

    1. Dissent says:
      July 29, 2016 at 9:46 pm

      Were you notified by the “unrelated web site,” too? If not, yeah, you should be concerned enough to insist Glassdoor tell you who the other site was so you can contact THEM and ask them what data of yours were compromised, etc. And if you used the same login credentials at a third or fourth or fifth site, better change all your passwords.

  5. Jim says:
    August 2, 2016 at 3:14 am

    Can someone forward me the email?

    1. Dissent says:
      August 2, 2016 at 7:50 am

      No, because I remove email addresses from submissions. I posted the notification email in the story itself.

Comments are closed.

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

  • ANNOUNCE: A new resource to help small and mid-sized HIPAA-regulated entities
  • Askul says 740,000 sets of data breached in cyberattack
  • Google and Apple roll out emergency security updates after zero-day attacks
  • Doxers Posing as Cops Are Tricking Big Tech Firms Into Sharing People’s Private Data
  • Virginia Urology Silent on Possible Data Breach as Purported Patient Data Begins to Leak
  • Village of Golf Manor considering paying ransom amid cyberattack (1)
  • Teen who allegedly stole millions of personal data records arrested in Spain
  • Akira ransomware: FBI tallies 250 million in payouts
  • IE: HSE confirms second ransomware attack but ‘no evidence’ patient data was stolen
  • Examining impact of federal relief program after major healthcare cyberattack — Research Brief

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

  • Slovenian officials weaponize data-privacy laws against investigative journalism
  • End-of-Year 2025 State and Federal Developments in Minors’ Privacy
  • Tool allows stealthy tracking of Signal and WhatsApp users through delivery receipts
  • Oh Great, Smart Glasses That Record Everything You Say
  • CBP Agents Held This U.S. Citizen for Hours Until He Agreed To Let Them Search His Electronic Devices

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: Dissent.73
DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.