LiveBreach Intelligence: data breaches, leaks & ransomware, tracked as they surfaceOngoing protection: GalaxyWarden →
Recent BreachesData breach tracker

Recent Breaches › Christian Dior Couture SAS Data Breach Notice (Oregon Attorney General)

MEDIUM severityConfirmedHow we verify

Christian Dior Couture SAS Data Breach Notice (Oregon Attorney General): What Was Exposed & What To Do

RBRecent Breaches Breach Intelligence·July 18, 2025
Christian Dior Couture SAS Data Breach Notice (Oregon Attorney General)

Occurred January 26, 2025 · publicly disclosed July 18, 2025. Approximately 79000 people affected.

MEDIUM
Severity
79000
People affected
1
Data types exposed
July 18, 2025
Disclosed
ShareXLinkedInFacebookRedditWhatsAppTelegram

Christian Dior Couture SAS reported a data breach to the Oregon Attorney General on July 18, 2025, after personal information of approximately 79,000 individuals was exposed in an incident that occurred on January 26, 2025. Individuals should review the notice and take steps to determine whether their information was involved and to protect against potential misuse.

Severity & verification
MEDIUM severityConfirmed
Data types not itemised.
Corroborated by an official disclosure or a verified breach feed.
Check your exposure
79000 accounts were exposed here. We can’t confirm any single incident against the sources we search — but we can show you every leak and listing tied to your email. 15-sec check, no card.

By running your scan you agree to the Terms and Conditions and the Privacy Policy, and to GalaxyWarden emailing you the results of this scan.

Luxury brands and their customer databases remain steady targets in a threat landscape where attackers chase high-value personal data that can be resold or reused for fraud. Against that backdrop, Christian Dior Couture SAS has disclosed a data incident affecting tens of thousands of people, according to a formal notice filed with a U.S. state regulator.

Public records show the company notified Oregon residents of a breach in a filing reported to the Oregon Department of Justice on July 18, 2025. The same filing dates the underlying incident to January 26, 2025, and states that roughly 79,000 people were affected. Exact technical details beyond that notice remain limited in the public record.

What happened

Christian Dior Couture SAS submitted a data-breach notice to the Oregon Attorney General’s office, reported on July 18, 2025. According to that filing, the incident itself occurred on January 26, 2025. The company informed Oregon residents that personal information was involved. The notice places the number of people affected at 79,000.

No further public detail in the cited filing describes how the intrusion was detected, which systems were touched, how long unauthorized access lasted, or whether data was exfiltrated, encrypted, or merely accessed. Method, root cause, and any containment steps are undisclosed in the available summary. No specific threat actor is named in the facts provided.

How a breach like this happens

Incidents of this general type often begin with common entry points: stolen or guessed credentials, phishing that tricks staff into revealing access, unpatched software on internet-facing systems, or compromised third-party vendors that hold customer records. Once inside a network, an attacker may move laterally, locate databases or file shares containing customer or employee information, and copy data for later use or sale.

Organizations typically discover such events through internal monitoring, unusual outbound traffic, ransomware notes, or notifications from law enforcement or security researchers. After discovery, standard practice includes isolating affected systems, determining what records were exposed, and issuing legally required notices to residents and regulators. None of these steps is confirmed as the sequence in this specific case; they describe how similar breaches commonly unfold when technical specifics are not public.

About Christian Dior Couture SAS

Christian Dior Couture SAS is the couture and high-fashion arm of the Dior brand, part of the global luxury sector. Companies in this space design, manufacture, and sell clothing, accessories, and related goods, and they routinely maintain customer accounts, purchase histories, loyalty or clienteling records, and contact details needed for sales, shipping, and marketing.

A breach at a luxury house matters because the customer base often includes high-net-worth individuals whose personal data can be especially useful for targeted fraud, social engineering, or identity misuse. Even when only a subset of records is confirmed exposed, the brand’s international footprint means notices may reach people across multiple jurisdictions, as illustrated by the Oregon filing.

The information in question

The breach notification names “personal information” as the category of data involved. The public summary does not itemize fields such as names, addresses, phone numbers, email addresses, dates of birth, government identifiers, payment card numbers, or purchase histories.

Organizations of this kind typically hold some combination of identity and contact data, account credentials or profile information, and transaction-related records. Because the filing does not list specific data elements beyond the broad label “personal information,” the exact contents remain unconfirmed. Readers should treat any assumption about particular fields as speculative until the company or regulators provide more detail.

Why it matters

For affected individuals, exposure of personal information can raise the risk of phishing, account takeover attempts, and identity fraud. Attackers who obtain names and contact details often craft convincing messages that reference a real brand relationship, increasing the chance that someone will click a malicious link or hand over further credentials. If additional identifiers were present—even if not confirmed here—the risk of new-account fraud or tax-related scams can rise.

For the organization, a disclosed incident can trigger regulatory scrutiny, notification costs, potential civil claims, and reputational strain among clients who expect discretion from a luxury house. The multi-month gap between the stated incident date (January 26, 2025) and the Oregon filing (July 18, 2025) is a matter of public record; any explanation for that interval is not included in the facts provided.

Concrete harm is not automatic. Many people whose data appears in a notice never experience direct financial loss. Still, elevated vigilance for a period after notice is a practical response, especially for anyone who has shopped with or held an account at the brand.

Were you affected?

If you are an Oregon resident or a Dior customer and believe you may be among the 79,000 people referenced, watch for an official notice from Christian Dior Couture SAS and follow any instructions it contains. Monitor financial and email accounts for unexpected activity, treat unsolicited messages that claim to be from the brand with caution, and consider placing a fraud alert or credit freeze if you are concerned about identity misuse. Change passwords on related accounts and enable multi-factor authentication where available.

You can also run a free exposure scan of your email address to check whether that address has already appeared in known breach datasets. Such scans do not replace official company notices, but they can help you decide whether further monitoring is warranted. Public detail on this incident remains limited to the Oregon filing; any future updates from the company or regulators should be read carefully if they expand on data types or affected populations.

AICompiled with AI assistance from public sources and published under our editorial standards.

Editorial & sourcing policy
Recent Breaches is a breach-monitoring service and news aggregator. We do not exfiltrate, host, purchase, or redistribute stolen data, and we do not hold the data claimed in leak-site listings. Incidents are compiled from publicly accessible sources and threat-intelligence platforms and are reported as claims attributed to their source. We promptly correct or remove material shown to be inaccurate — write to support@galaxywarden.com or press@recentbreaches.com.
Check if you’re exposed →

How this breach connects

Company

CompanyChristian Dior Couture SAS security record
74/100
DoxxScan™ · Moderate doxx risk
B 80Good record

1 reported incident on record.

See Christian Dior Couture SAS’s full breach history →

More recent breaches

Decisely Insurance Services Data Breach Notice (Oregon Attorney General)December 30, 2025Apro, LLC d/ Data Breach Notice (Oregon Attorney General)December 29, 2025Apro, LLC d/b/a United Pacific Data Breach Notice (Oregon Attorney General)December 29, 2025CareOregon Data Breach Notice (Oregon Attorney General)December 26, 2025

Latest breaches

Read GalaxyWarden’s full analysis of the Christian Dior Couture SAS Data Breach Notice (Oregon Attorney General) →

Source: Oregon Department of Justice breach notification

Verified breach

Breach listings — particularly those originating from ransomware or leak sites — are third-party claims that may be unverified, incomplete, or inaccurate. A listing does not by itself confirm that a breach occurred or that any specific data was exposed. Severity is an automated assessment, not a definitive rating. Verification status is shown where available.

Attributions to threat groups and methods reflect public reporting and, in some cases, unverified claims made by the groups themselves; they may be incomplete or later revised. Recent Breaches and GalaxyWarden are independent and are not affiliated with, and do not endorse, any company or group named on this page. This information is aggregated from public sources for awareness only and is not legal, security, or investment advice.

ShareXLinkedInFacebookRedditWhatsAppTelegram