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

New York Blood Center Enterprises — January 2025 breach

Clustered 13 filings across 13 jurisdictions · filing window Sep 1, 2025 → Sep 9, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

13 filings

States

13

Affected · reported

193,822

First → last filing

Sep 1, 2025 → Sep 9, 2025

Merge confidence

100%

incident inc_c5b9bf500ce34c32 · merged by human · confidence 100%

Confirmed breach. Merged as one breach: 13 regulatory filings. Intrusion Jan 20, 2025–Jan 26, 2025, discovered Jan 26, 2025 — the first regulatory filing landed 218 days later (flagged late). 193,822 individuals reported across the linked filings. Data reported: Government ID, Financial account, Health (basic), and 3 more. Notifications rolled out on a 8-day schedule across 13 filings beginning Sep 1, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
218days

Discovered → first regulatory filing

Discovery variance
155days

Range of discovered_at dates across filings

Filing span
8days

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 clocksWashington✗ WA AG >90dOregon✗ OR AG >45dTexas✗ TX AG >30dRhode Island✗ RI AG >45dMaine⏱ ME AG >30d · 67dMassachusetts✓ MA credit monitoring dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 20, 2025breach begins
Jan 26, 2025discovered · members disagree
notification delay · 218 days
Sep 1, 2025first filing
Sep 9, 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. SEP 1IL AGIL AG noticefirst filing · no count statedday 0
  2. SEP 5WA AGWA AG notice2,996 WA residents+4d
  3. SEP 5NE AGNE AG notice312 NE residents+4d
  4. SEP 5MA AGMA AG notice213 MA residents+4d
  5. SEP 5ME AGME AG notice8 ME residents+4d
  6. SEP 5DE AGDE AG noticeno count stated+4d
  7. SEP 5OR AGOR AG noticestates nationwide total 193,822+4d
  8. SEP 5NH AGNH AG notice6 NH residents+4d
  9. SEP 5IN AGIN AG notice6 IN residents+4d
  10. SEP 5MT AGMT AG notice658 MT residents+4d
  11. SEP 5CA AGCA AG noticeno count stated+4d
  12. SEP 9TX AGTX AG noticestates nationwide total 193,822+8d
  13. SEP 9RI AGRI AG noticemost recent · 1,122 RI residents+8d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Jan 20, 2025 – Jan 26, 2025
WA AG
Discovered
Jan 26, 2025WA AG + NE AG + DE AG +5Jun 30, 2025IL AG + ME AG + OR AGfilings disagree on discovery
Data types
Employment · Financial account · Health (basic) · Identity (basic) · Government ID · PHI
IL AG + WA AG + NE AG +8
Attack vector
Ransomware
WA 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)

193,822

Sum of filed state slices

15,878· 8.2% of stated

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

US193,822
TX10,557
WA2,996
RI1,122
MT658
NE312
MA213
ME8
NH6
IN6

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

8 days

Cadence

~1 / 0.7d

vs. multi-state median

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