DataBreaches.Net

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

(update) Lush Looks For Answers In Security Breach That Could Cost Customers Thousands

Posted on January 22, 2011 by Dissent

Popular cosmetics chain Lush has been attacked by hackers, with consumer credit card information and personal details having been used for fraudulent purchases. It appears as though the hackers may have been stealing sensitive data for up to four months, and Lush has advised consumers to contact their banks if they thought their details had been used by the hackers.

On January 21st, a message on the Lush home page explained the situation and the online shop were shut down. Based on what people are saying on Lush’s Facebook fan page, people are far from happy. People complained about having to cancel their credit cards from fear of exploitation and many claimed to have lost money as well. The biggest complaint seems to be that Lush took so long in noticing the breach in security.

Read more on Reviews of Electronics.

H/T, DataLossDB.org


Related:

  • Landmark civil penalty of AU$5.8 million issued under Australia’s Privacy Act
  • Legal Aid Agency chief admits difficulties understanding impact of cyberattack
  • Revealed: Afghan data breach after MoD official left laptop open on train
  • Snowflake Loses Two More Bids to Dismiss Data Breach Plaintiffs
  • US company with access to biggest telecom firms uncovers breach by nation-state hackers
  • Canada says hacktivists breached water and energy facilities
Category: Breach IncidentsBusiness SectorHackNon-U.S.

Post navigation

← Criminal finance database security worries peers
UK: Somerset schools’ website security ‘breached’ by Southwest One →

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.