Now Hacked
EN-GB
Data breach

Dior customer data leaked via breach of customer management service

First reported · Last reported · 29 related reports

Customer personal data was leaked at Dior in January 2025, but the company only became aware of the incident in May. Employee credentials used to access an external customer management service were misused, exposing customer names, phone numbers, addresses, purchase information and more. Dior notified and apologised to affected customers, saying financial account and card details were not included in the breach.

Key facts

Affected organisation
Dior
Incident type
Data breach
Occurred / detected
Not confirmed
Scale of damage
Personal data including customer names, phone numbers, addresses and purchase information
Cause / method
Misuse of employee credentials used to access an external customer management service
Location
South Korea

If your data was exposed

Exposed dataNamePhone numberAddressUsage & purchase history

  1. Don’t tap links in texts, calls or emails that mention this incident and offer compensation, refunds or breach checks. Check directly on the organisation’s official website or app.
  2. If you’ve suffered harm, report it. Call 118 (no area code) for privacy violations, contact the police for financial losses, and apply for dispute mediation to seek compensation.Personal Information Infringement Report Centre ↗Korean National Police Agency cybercrime report ↗Personal Information Dispute Mediation Committee ↗

Timeline

  1. The leak of Dior customers' names, addresses and phone numbers and the delay in announcing the incident came to light.
  2. It emerged that employee credentials had been misused and that the January breach was detected in May.
  3. Dior formally notified customers of the hack of their personal data.
  4. It was reported that Dior, Louis Vuitton and Tiffany had been fined a total of US$25 million in South Korea over personal data breaches.

29 related reports

The summary and key facts are written by AI from related reports and may contain errors. Check the original articles and the organisation’s official statements for accurate details.