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

California Cryobank — April 2024 breach

Clustered 9 filings across 9 jurisdictions · filed Mar 14, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

9 filings

States

9

Affected · reported

11,246

First → last filing

Mar 14, 2025

Merge confidence

100%

incident inc_2ad2cb1da09247e4 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings. The filings describe unauthorized access. Intrusion Apr 20, 2024–Apr 22, 2024, discovered Apr 21, 2024 — the first regulatory filing landed 327 days later (flagged late). 11,246 individuals reported across the linked filings. Data reported: Government ID, Financial account, PCI, and 3 more. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
327days

Discovered → first regulatory filing

Discovery variance
166days

Range of discovered_at dates across filings

Filing span
0days

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 clocksCalifornia✗ CA 60-day late · 327dVermont✗ VT AG >45 bdayMaine✗ ME AG >90d · 327dMaryland✗ MD AG >90dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Apr 20, 2024breach begins
Apr 21, 2024discovered · members disagree
notification delay · 327 days
Mar 14, 2025first filing
—watching for filings

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

Member cascade — every filing about this breach

  1. MAR 14MA AGMA AG noticefirst filing · 195 MA residentsday 0
  2. MAR 14IN AGIN AG noticestates nationwide total 11,246day 0
  3. MAR 14MT AGMT AG notice24 MT residentsday 0
  4. MAR 14CA AGCA AG noticeno count statedday 0
  5. MAR 14NE AGNE AG noticeno count statedday 0
  6. MAR 14NH AGNH AG noticeno count statedday 0
  7. MAR 14VT AGVT AG noticeno count statedday 0
  8. MAR 14ME AGME AG notice28 ME residentsday 0
  9. MAR 14MD AGMD AG noticemost recent · no count statedday 0
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Apr 20, 2024
IN AG
Discovered
Apr 21, 2024MT AG + CA AG + NH AG +3Oct 4, 2024NE AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PCI · PHI
MA AG + CA AG + NH 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)

11,246

Sum of filed state slices

283· 2.5% of stated

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

US11,246
MA195
IN36
ME28
MT24

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

0 days

Cadence

~1 / 0d

vs. multi-state median

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