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

Delta Dental of Virginia — March 2025 breach

Clustered 12 filings across 12 jurisdictions · filing window Jan 21, 2025 → Nov 21, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

12 filings

States

12

Affected · reported

145,918

First → last filing

Jan 21, 2025 → Nov 21, 2025

Merge confidence

100%

incident inc_a6d83117899e44ba · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 12 regulatory filings. Intrusion Mar 21, 2025–Apr 23, 2025, discovered Apr 23, 2025. 145,918 individuals reported across the linked filings. Data reported: Government ID, PII, Identity (basic), and 4 more. Notifications rolled out on a 304-day schedule across 12 filings beginning Jan 21, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
152days

Range of discovered_at dates across filings

Filing span
304days

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 bdayMaine✗ ME AG >90d · 212dHIPAA✓ HHS notifiedMassachusetts✓ MA credit monitoring dueSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Mar 21, 2025breach begins
Apr 23, 2025discovered · members disagree
Jan 21, 2025first filing
Nov 21, 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. JAN 21MT AGMT AG noticefirst filing · 125 MT residentsday 0
  2. NOV 1IL AGIL AG noticeno count stated+284d
  3. NOV 21CA AGCA AG noticeno count stated+304d
  4. NOV 21VT AGVT AG noticeno count stated+304d
  5. NOV 21NE AGNE AG notice140 NE residents+304d
  6. NOV 21HHS OCRHHS OCR noticestates nationwide total 126,953+304d
  7. NOV 21MA AGMA AG notice628 MA residents+304d
  8. NOV 21NH AGNH AG notice169 NH residents+304d
  9. NOV 21IN AGIN AG noticestates nationwide total 145,918+304d
  10. NOV 21ME AGME AG noticestates nationwide total 145,918+304d
  11. NOV 21SC AGSC AG notice1,413 SC residents+304d
  12. NOV 21TX AGTX AG noticemost recent · states nationwide total 145,918+304d
  13. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 21, 2025 – Apr 23, 2025
MT AG
Discovered
Apr 23, 2025MT AG + IL AG + CA AG +5Sep 22, 2025TX AGfilings disagree on discovery
Data types
Credentials · Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
MT AG + CA AG + VT AG +8
Attack vector
Phishing
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)

145,918

Sum of filed state slices

5,699· 3.9% of stated

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

US145,918
TX2,374
SC1,413
MA628
IN628
ME222
NH169
NE140
MT125

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

304 days

Cadence

~1 / 27.6d

vs. multi-state median

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