
Dior’s Database Was Accessed in January. The Company Identified the Incident in May.
The customer-data attack crossed jurisdictions and produced different consequences: a Korean regulatory penalty and a U.S. settlement process. The timeline shows why containing an intrusion is only one stage of responding to stolen client information.
January 26 and May 7 describe different moments in Dior’s breach. The first was the unauthorized database access identified by its investigation. The second was when the fashion house identified a potential incident. Between them lay more than three months.
That gap appears in the company’s own account of the incident in its U.S. settlement agreement. It later became central to South Korean regulators’ account of failures in the brand’s customer-management safeguards. The criminal intrusion and the company’s detection were separate events; reporting the discovery date as the attack date would erase the interval.
The notice described names, contact details, addresses, dates of birth and, for some customers, government identification information. A version filed in Massachusetts also described Social Security numbers in a small number of cases. Payment information was not held in the accessed database. Dior said outside experts had verified containment and found no evidence of unauthorized access beyond January 26.
Containment did not mean customers could treat all the copied fields as harmless. An identification number and a shopping preference do not create the same exposure, and neither is equivalent to a compromised payment card. Recipient-specific notices matter because a brand-wide description can hide those differences. The Massachusetts version offered 24 months of credit monitoring rather than asserting that every recipient had already suffered identity theft.
The international disclosures also revealed how much information a retailer can collect around a sale. Marketing-Interactive’s account of a Chinese customer notice described purchase amounts and shopping preferences alongside contact information. It reported that the brand apologized and warned customers about suspicious communications. Those were fields described in that market’s notification, not proof that every Dior client worldwide had an identical record.
The Korean privacy regulator’s February 2026 decision found that voice phishing secured customer-management access, exposing approximately 1.95 million people’s information. It identified missing access/download restrictions, deficient log review and notification beyond 72 hours. Christian Dior Couture Korea received a 12.236 billion-won penalty and separate 3.6 million-won fine.
Yonhap reported the sanctions alongside actions against two other luxury businesses. The industry total is not Dior’s individual penalty. Nor is an administrative sanction a compensation payment to each customer: the regulator’s remedy and a consumer’s recovery answer different questions.
In the United States, a separate civil process developed. The settlement agreement in Michael Toikach and others v. Christian Dior describes written notifications to approximately 78,000 affected U.S. individuals around July 18, 2025. That figure is not interchangeable with the Korean regulator’s count.
The court-authorized settlement notice set out benefits for eligible U.S. recipients, including a $100 payment for the tier whose Social Security numbers were affected. It said Dior denied wrongdoing and the court had not decided which side was right. A settlement offers a route to benefits without establishing every allegation in a contested liability trial.
The notice also offered reimbursement of documented losses up to $1,500, tied to eligible fraud or identity-theft costs within a defined period. It required supporting evidence and excluded expenses already reimbursed elsewhere. The distinction was consequential: eligibility for a settlement did not make every recipient entitled to the maximum payment, and the maximum was not a valuation of every stolen record.
The administrator’s website listed a May 25, 2026, claims deadline and a June 22 final-approval hearing. Its public notice continued to describe approval as outstanding on November 16. The scheduled hearing date alone does not establish final approval or payments to claimants.
The corporate cost of the attack therefore appears in several forms, none a complete substitute for the others: investigation, notification, a regulatory sanction and a proposed civil remedy. For a client deciding what happened to information entrusted to Dior, the starting point remains the two dates. The database was accessed in January. The company identified the incident in May. Everything that followed had to address information that had already left its intended custody.
Compiled November 16, 2026. Records and findings keep the dates stated in their sources; each link in the text opens the document it relies on.