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

CITY OF HOPE — July 2023 breach

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

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

9

Affected · reported

827,149

First → last filing

Apr 1, 2024 → Apr 16, 2024

Merge confidence

100%

incident inc_a51d7cc0564747a9 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 10 regulatory filings. The filings describe unauthorized access. Intrusion Jul 7, 2023–Oct 15, 2023, discovered Oct 13, 2023 — the first regulatory filing landed 171 days later (flagged late). 827,149 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 4 more. Notifications rolled out on a 15-day schedule across 10 filings beginning Apr 1, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
171days

Discovered → first regulatory filing

Discovery variance
164days

Range of discovered_at dates across filings

Filing span
15days

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 >45 bdayWashington✗ WA AG >90dMaine✓ ME AG ≤30d · 8dMassachusetts✓ MA credit monitoring dueOregon✓ OR AG ≤45dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jul 7, 2023breach begins
Oct 13, 2023discovered · members disagree
notification delay · 171 days
Apr 1, 2024first filing
Apr 16, 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. APR 1IL AGIL AG noticefirst filing · no count statedday 0
  2. APR 2NH AGNH AG notice181 NH residents+1d
  3. APR 2MT AGMT AG notice580 MT residents+1d
  4. APR 2VT AGVT AG noticeno count stated+1d
  5. APR 2CA AGCA AG noticeno count stated+1d
  6. APR 2ME AGME AG noticestates nationwide total 827,149+1d
  7. APR 2WA AGWA AG notice3,784 WA residents+1d
  8. APR 3MA AGMA AG notice1,066 MA residents+2d
  9. APR 3OR AGOR AG noticeno count stated+2d
  10. APR 16OR AGOR AG noticemost recent · states nationwide total 827,149+15d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Sep 19, 2023 – Oct 12, 2023
NH AG
Discovered
Oct 13, 2023IL AG + NH AG + MT AG +3Mar 25, 2024ME AG + OR AGfilings disagree on discovery
Data types
Education · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
NH AG + MT AG + VT AG +4
Attack vector
Unauthorized Access
NH 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)

827,149

Sum of filed state slices

5,777· 0.7% of stated

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

US827,149
WA3,784
MA1,066
MT580
NH181
ME166

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

15 days

Cadence

~1 / 1.7d

vs. multi-state median

1.7× 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.