Christian Dior Couture — January 2025 breach

Clustered 8 filings across 8 jurisdictions · filing window Jul 18, 2025 → Jul 22, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

8 filings

States

Affected · reported

79,000

First → last filing

Jul 18, 2025 → Jul 22, 2025

Merge confidence

100%

incident inc_292d44f0cb764c19 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings. Intrusion Jan 26, 2025, discovered May 7, 2025 — the first regulatory filing landed 72 days later (flagged late). 79,000 individuals reported across the linked filings. Data reported: Government ID and Identity (basic). Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

72days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Filing span

4days

Time between earliest and latest filing

Not recorded for this incident

Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.

Regulatory clocksOregon✗ OR AG >45dVermont✗ VT AG >45 bdayTexas✗ TX AG >30dWashington⏱ WA AG >30dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

No cross-filing comparison data available for this incident.

The weekly clock on records like this one

The Disclosure Clock is a weekly briefing on what landed in the disclosure record, and the gap between the criminals' post and the regulator's filing — measured on the whole record, with the method shown.

Weekly. Double opt-in, one-click unsubscribe, and the address goes nowhere else.