DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed11 filings · 11 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 11 filings

Louis Vuitton North America, Inc. — June 2025 breach

Clustered 11 filings across 11 jurisdictions · filing window Aug 22, 2025 → Aug 26, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

11 filings

States

11

Affected · reported

172,000

First → last filing

Aug 22, 2025 → Aug 26, 2025

Merge confidence

100%

incident inc_7e7aa958397f480c · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 11 regulatory filings. The filings describe unauthorized access. Intrusion Jun 7, 2025–Jun 13, 2025, discovered Jul 2, 2025 — the first regulatory filing landed 51 days later (flagged late). 172,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

Notification delay
51days

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 >14 bdayWashington⏱ WA AG >30dSouth Carolina✓ SC CRA notice dueCalifornia✓ CA 60-day OK · 51dTexas✓ TX CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jun 7, 2025breach begins
Jul 2, 2025discovered
notification delay · 51 days
Aug 22, 2025first filing
Aug 26, 2025most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. AUG 22MA AGMA AG noticefirst filing · 4 MA residentsday 0
  2. AUG 22OR AGOR AG noticestates nationwide total 172,000day 0
  3. AUG 22IN AGIN AG noticestates nationwide total 172,000day 0
  4. AUG 22DE AGDE AG noticeno count statedday 0
  5. AUG 22NE AGNE AG noticeno count statedday 0
  6. AUG 22SC AGSC AG notice2,103 SC residentsday 0
  7. AUG 22VT AGVT AG noticeno count statedday 0
  8. AUG 22NH AGNH AG notice525 NH residentsday 0
  9. AUG 22CA AGCA AG noticeno count statedday 0
  10. AUG 22WA AGWA AG notice17,615 WA residentsday 0
  11. AUG 26TX AGTX AG noticemost recent · states nationwide total 172,000+4d
  12. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jun 7, 2025 – Jun 13, 2025
OR AG
Discovered
Jul 2, 2025· 25d undetected
OR AG + DE AG + NE AG +6
Data types
Identity (basic) · Government ID
MA AG + DE AG + NE AG +6
Attack vector
Unauthorized Access
DE AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

172,000

Sum of filed state slices

43,821· 25.5% of stated

75% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

US172,000
TX23,570
WA17,615
SC2,103
NH525
MA4
IN4

State AGs report only their own residents; teal bars show each state's reported slice. The gray US row is the nationwide total reported in a linked filing.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing11 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Jun 12, 2026 · at least one link edge was human-adjudicated
Audit
Every link edge records its method, confidence and model + prompt versions (100% is the strongest edge).

Merges are reversible — a wrong link can be detached with its audit trail intact. How merging works.

Filing velocity

Spread

4 days

Cadence

~1 / 0.4d

vs. multi-state median

2.0× faster

About this clustering

DisclosureLens links filings into incidents through layered matchers: deterministic rules (same source document, multistate filings of one breach, tight-window same-victim pairs), a weighted-similarity scorer for cross-source candidates, and an operator review queue for everything uncertain. Each link records its own method and confidence — shown per filing in the timeline below. The system defaults to NOT merging when uncertain, because a false merge (collapsing two unrelated breaches) is more harmful than a false split (showing related filings separately); uncertain pairs route to human review instead of auto-merging. This page states only what the linked filings agree on; each filing's own account stays on its own record, linked from the timeline below.

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.