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.

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

  • Ransomware Attack on ADP Partner Exposes Broadcom Employee Data
  • Anne Arundel ransomware attack compromised confidential health data, county says
  • Australian national known as “DR32” sentenced in U.S. federal court
  • Alabama Man Sentenced to 14 Months in Connection with Securities and Exchange Commission X Hack that Spiked Bitcoin Prices
  • Japan enacts new Active Cyberdefense Law allowing for offensive cyber operations
  • Breachforums Boss “Pompompurin” to Pay $700k in Healthcare Breach
  • HHS Office for Civil Rights Settles HIPAA Cybersecurity Investigation with Vision Upright MRI
  • Additional 12 Defendants Charged in RICO Conspiracy for over $263 Million Cryptocurrency Thefts, Money Laundering, Home Break-Ins
  • RIBridges firewall worked. But forensic report says hundreds of alarms went unnoticed by Deloitte.
  • Chinese Hackers Hit Drone Sector in Supply Chain Attacks

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

  • Massachusetts Senate Committee Approves Robust Comprehensive Privacy Law
  • Montana Becomes First State to Close the Law Enforcement Data Broker Loophole
  • Privacy enforcement under Andrew Ferguson’s FTC
  • “We would be less confidential than Google” – Proton threatens to quit Switzerland over new surveillance law
  • CFPB Quietly Kills Rule to Shield Americans From Data Brokers
  • South Korea fines Temu for data protection violations
  • The BR Privacy & Security Download: May 2025

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.