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

Christie's Inc. — May 2024 breach

Clustered 10 filings across 10 jurisdictions · filing window Jun 1, 2024 → Jun 14, 2024. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

10

Affected · reported

45,798

First → last filing

Jun 1, 2024 → Jun 14, 2024

Merge confidence

100%

incident inc_c7388928503f48d0 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. Intrusion May 8, 2024–May 9, 2024, discovered May 8, 2024 — the first regulatory filing landed 24 days later. 45,798 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), and PII. Notifications rolled out on a 13-day schedule across 10 filings beginning Jun 1, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Notification delay
24days

Discovered → first regulatory filing

Discovery variance
1days

Range of discovered_at dates across filings

Filing span
13days

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 clocksVermont⏱ VT AG >14 bdayMaine✓ ME AG ≤30d · 29dCalifornia✓ CA 60-day OK · 21dWashington✓ WA AG ≤30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

May 8, 2024breach begins
May 8, 2024discovered · members disagree
notification delay · 24 days
Jun 1, 2024first filing
Jun 14, 2024most 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. JUN 1IL AGIL AG noticefirst filing · no count statedday 0
  2. JUN 7MA AGMA AG notice1,379 MA residents+6d
  3. JUN 7MT AGMT AG notice85 MT residents+6d
  4. JUN 7ME AGME AG noticestates nationwide total 45,798+6d
  5. JUN 7CA AGCA AG noticeno count stated+6d
  6. JUN 7OR AGOR AG noticestates nationwide total 45,798+6d
  7. JUN 7WA AGWA AG notice985 WA residents+6d
  8. JUN 7VT AGVT AG noticeno count stated+6d
  9. JUN 7IN AGIN AG noticestates nationwide total 45,798+6d
  10. JUN 14NH AGNH AG noticemost recent · 185 NH residents+13d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
May 8, 2024 – May 9, 2024
MT AG
Discovered
May 8, 2024IL AGMay 9, 2024MT AG + ME AG + CA AG +3filings disagree on discovery
Data types
Identity (basic) · Government ID · PII
MA AG + ME 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)

45,798

Sum of filed state slices

3,152· 6.9% of stated

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

US45,798
MA1,379
WA985
IN363
NH185
ME155
MT85

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

13 days

Cadence

~1 / 1.4d

vs. multi-state median

1.4× slower

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.