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

Vivendi Ticketing US, LLC — February 2023 breach

Clustered 10 filings across 10 jurisdictions · filing window Sep 5, 2023 → Sep 6, 2023. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

323,498

First → last filing

Sep 5, 2023 → Sep 6, 2023

Merge confidence

100%

incident inc_23926262b2694e02 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe unauthorized access. Intrusion Feb 28, 2023–Jul 2, 2023, discovered May 1, 2023 — the first regulatory filing landed 127 days later (flagged late). 323,498 individuals reported across the linked filings. Data reported: PII, Financial account, Identity (basic), and 2 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
127days

Discovered → first regulatory filing

Discovery variance
81days

Range of discovered_at dates across filings

Filing span
1days

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 bdayWashington✗ WA AG >90dMaine⏱ ME AG >30d · 47dSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

financial_credentials

Incident timeline

Feb 28, 2023breach begins
May 1, 2023discovered · members disagree
notification delay · 127 days
Sep 5, 2023first filing
Sep 6, 2023most 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. SEP 5IN AGIN AG noticefirst filing · states nationwide total 323,498day 0
  2. SEP 5MT AGMT AG notice219 MT residentsday 0
  3. SEP 5OR AGOR AG noticestates nationwide total 323,498day 0
  4. SEP 5VT AGVT AG noticeno count statedday 0
  5. SEP 5CA AGCA AG noticeno count statedday 0
  6. SEP 5NH AGNH AG notice1,606 NH residentsday 0
  7. SEP 5WA AGWA AG notice16,450 WA residentsday 0
  8. SEP 6SC AGSC AG notice1,428 SC residents+1d
  9. SEP 6ME AGME AG noticestates nationwide total 323,498+1d
  10. SEP 6MA AGMA AG noticemost recent · 8,805 MA residents+1d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Feb 28, 2023
IN AG
Discovered
May 1, 2023MT AG + VT AG + NH AG +1May 16, 2023WA AGJul 21, 2023OR AG + ME AGfilings disagree on discovery
Data types
Financial account · Financial credentials · Identity (basic) · PCI · PII
MT AG + VT AG + WA AG +4
Attack vector
Unauthorized Access
MT 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)

323,498

Sum of filed state slices

35,662· 11.0% of stated

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

US323,498
WA16,450
MA8,805
IN6,595
NH1,606
SC1,428
ME559
MT219

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 filing10 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
human
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Oct 22, 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

1 days

Cadence

~1 / 0.1d

vs. multi-state median

6.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.