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

Navia Benefit Solutions, Inc. — December 2025 breach

Clustered 18 filings across 14 jurisdictions · filing window Mar 18, 2026 → Mar 30, 2026 (dated filings only). View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

18 filings

States

14

Affected · reported

2,697,540

First → last dated filing

Mar 18, 2026 → Mar 30, 2026

Merge confidence

100%

incident inc_f2415c30e4db44e2 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 18 regulatory filings. The filings describe unauthorized access. Intrusion Dec 22, 2025–Jan 15, 2026, discovered Jan 23, 2026. 2,697,540 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PII, and 4 more. Notifications rolled out on a 12-day schedule across 16 dated filings beginning Mar 18, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Discovery variance
0days

Range of discovered_at dates across filings

Filing span
12days

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 clocksOregon✗ OR AG >45dVermont⏱ VT AG >14 bdayMaine⏱ ME AG >30d · 54dWashington⏱ WA AG >30dHIPAA✓ HHS notifiedIowa✓ IA AG ≤5 bdayTexas✓ TX CRA notice dueFull clock table in Litigation Timeline

Sensitive data

authenticationidentity_government

Incident timeline

Dec 22, 2025breach begins
Jan 23, 2026discovered
Mar 18, 2026first dated filing
Mar 30, 2026most recent dated filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident. Filings without a recorded filing day, or recorded as filed before the breach they report began, are not placed on this rail.

Member cascade — every filing about this breach

  1. MAR 1IL AGIL AG noticefiling day not on record · no count stated—
  2. MAR 18NH AGNH AG noticefirst filing · 1,351 NH residentsday 0
  3. MAR 18NE AGNE AG noticefiling day not on record · 17,485 NE residents—
  4. MAR 18MA AGMA AG notice37,498 MA residentsday 0
  5. MAR 18VT AGVT AG noticeno count statedday 0
  6. MAR 18OR AGOR AG noticestates nationwide total 2,697,540day 0
  7. MAR 18MT AGMT AG notice1,117 MT residentsday 0
  8. MAR 18IN AGIN AG notice6,088 IN residentsday 0
  9. MAR 18CA AGCA AG noticeno count statedday 0
  10. MAR 18HHS OCRHHS OCR noticestates nationwide total 2,151,330day 0
  11. MAR 18ME AGME AG noticestates nationwide total 2,697,540day 0
  12. MAR 18WA AGWA AG notice319,208 WA residentsday 0
  13. MAR 18DE AGDE AG noticeno count statedday 0
  14. MAR 18IA AGIA AG notice2,718 IA residentsday 0
  15. MAR 20TX AGTX AG noticestates nationwide total 2,697,540+2d
  16. MAR 23WA AGWA AG notice1,100 WA residents+5d
  17. MAR 23VT AGVT AG noticeno count stated+5d
  18. MAR 30NH AGNH AG noticemost recent · 5 NH residents+12d
  19. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 22, 2025 – Jan 15, 2026
NH AG
Discovered
Jan 23, 2026· 32d undetected
IL AG + NH AG + NE AG +8
Data types
Authentication · Employment · Health (basic) · Identity (basic) · Government ID · PHI · PII
IL AG + NH AG + NE AG +10
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)

2,697,540

Sum of filed state slices

449,119· 16.6% of stated

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

US2,697,540
WA319,208
TX62,821
MA37,498
NE17,485
IN6,088
IA2,718
NH1,351
MT1,117
ME833

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 filing18 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 Aug 26, 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

12 days

Cadence

~1 / 0.8d

vs. multi-state median

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