DataBreaches.Net

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

CORRECTED: When was Epsilon breached?

Posted on April 6, 2011 by Dissent

Curiouser and curiouser.

TripAdvisor.com reported a breach on March 24.  At the time, some sources suggested it was a SQL injection, although I mentioned that there was some possibility it was due to a breach at an email service provider.  Now TripAdvisor.com has sent out notices that they have been affected by the Epsilon breach. CORRECTION: The breach report I had been sent supposedly related to Epsilon was the March 24th notice which is not Epsilon. My apologies to Epsilon and TripAdvisor.

Rest deleted as now irrelevant.

No related posts.

Category: Breach IncidentsBusiness SectorHackSubcontractorU.S.

Post navigation

← Have you gotten a phishing phone call after the Epsilon breach? (updated)
US Airways Pilots Express Outrage over Data Theft →

2 thoughts on “CORRECTED: When was Epsilon breached?”

  1. Neil Schwartzman says:
    April 6, 2011 at 9:45 am

    Sigh. As far as I know, Epsilon are not the ESP for TripAdviser. That was ExactTarget, another ESP. You haven’t yet posted the data related to TripAdviser on your list at http://www.databreaches.net/?p=17374 – if you have something to prove me wrong, I’d like to see it.

    1. admin says:
      April 6, 2011 at 1:02 pm

      Damn. I had linked TripAdvisor to ExactTarget in an earlier blog entry, but someone told me they got a TripAdvisor notice related to Epsilon. They forwarded it to me but I didn’t read it carefully enough. They forwarded me the March 24th notification which doesn’t name Epsilon. Gah. Let me correct what needs to be corrected. Thanks for calling it to my attention.

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

  • Russia Jailed Hacker Who Worked for Ukrainian Intelligence to Launch Cyberattacks on Critical Infrastructure
  • Kentfield Hospital victim of cyberattack by World Leaks, patient data involved
  • India’s Max Financial says hacker accessed customer data from its insurance unit
  • Brazil’s central bank service provider hacked, $140M stolen
  • Iranian and Pro-Regime Cyberattacks Against Americans (2011-Present)
  • Nigerian National Pleads Guilty to International Fraud Scheme that Defrauded Elderly U.S. Victims
  • Nova Scotia Power Data Breach Exposed Information of 280,000 Customers
  • No need to hack when it’s leaking: Brandt Kettwick Defense edition
  • SK Telecom to be fined for late data breach report, ordered to waive cancellation fees, criminal investigation into them launched
  • Louis Vuitton Korea suffers cyberattack as customer data leaked

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

  • On July 7, Gemini AI will access your WhatsApp and more. Learn how to disable it on Android.
  • German court awards Facebook user €5,000 for data protection violations
  • Record-Breaking $1.55M CCPA Settlement Against Health Information Website Publisher
  • Ninth Circuit Reviews Website Tracking Class Actions and the Reach of California’s Privacy Law
  • US healthcare offshoring: Navigating patient data privacy laws and regulations
  • Data breach reveals Catwatchful ‘stalkerware’ is spying on thousands of phones
  • Google Trackers: What You Can Actually Escape And What You Can’t

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.