DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
Leak SiteHHS OCRSEC 8-KState AGConfirmed10 filings · 9 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedinterlockhigh sensitivity
Merged incident · 10 filings

DAVITA INC. — March 2025 breach

Clustered 10 filings across 10 jurisdictions · filing window Apr 12, 2025 → Aug 4, 2025. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

10 filings

States

9

Affected · reported

2,689,826

First → last filing

Apr 12, 2025 → Aug 4, 2025

Merge confidence

100%

incident inc_19657f8388ea4bd3 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 9 regulatory filings and 1 unverified claim. Intrusion Mar 24, 2025–Apr 12, 2025, discovered Apr 12, 2025 — the first regulatory filing landed 2 days later (flagged late). 2,689,826 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 2 more. Notifications rolled out on a 114-day schedule across 9 filings beginning Apr 12, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
2days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
2days before filing

Days between the first leak-site claim and the first regulatory filing. Positive = the claim came first (public exposure before disclosure). Negative = the claim trailed the filing, so there was no pre-disclosure leak. Counts regulatory filings only — press coverage is not a regulatory disclosure.

Filing span
114days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay

Regulatory clocksOregon✗ OR AG >45dWashington✗ WA AG >90dTexas✗ TX AG >30dLeak gap⏱ Leak >90dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 24, 2025breach begins
Apr 12, 2025discovered
notification delay · 2 days
Apr 14, 2025first filing
Aug 4, 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. APR 12Leak siteinterlock postfirst filing · attacker claim · unverifiedday 0
  2. APR 14SEC 8-KSEC 8-K noticeno count stated+2d
  3. AUG 1HHS OCRHHS OCR noticestates nationwide total 2,689,826+111d
  4. AUG 1SC AGSC AG notice11,570 SC residents+111d
  5. AUG 1OR AGOR AG noticestates nationwide total 915,952+111d
  6. AUG 1WA AGWA AG notice13,404 WA residents+111d
  7. AUG 1MA AGMA AG notice7,829 MA residents+111d
  8. AUG 1NE AGNE AG noticeno count stated+111d
  9. AUG 1MT AGMT AG notice761 MT residents+111d
  10. AUG 4TX AGTX AG noticemost recent · states nationwide total 915,952+114d
  11. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 24, 2025 – Apr 12, 2025
SC AG
Discovered
Apr 12, 2025· 19d undetected
SEC 8-K + SC AG + OR AG +4
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
HHS OCR + SC AG + WA AG +4
Attack vector
Ransomware
SEC 8-K

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)

2,689,826

Sum of filed state slices

115,304· 4.3% of stated

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

US2,689,826
TX81,740
WA13,404
SC11,570
MA7,829
MT761

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

Attacker assertion only. Establishes: claim date, group, alleged victim.

Press / market report

No press coverage linked yet.

State AG / regulator filing8 members

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement1 member

Unlocks: materiality, stated response, full audit trail. Ceiling removed.

Merge provenance

Method
deterministic
Confidence
1.00 · above the 0.85 auto-merge floor
Reviewed
operator-reviewed Aug 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

114 days

Cadence

~1 / 12.7d

vs. multi-state median

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