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

TriZetto Provider Solutions — November 2024 breach

Clustered 13 filings across 12 jurisdictions · filing window Feb 6, 2026 → Mar 5, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

13 filings

States

12

Affected · reported

3,433,965

First → last filing

Feb 6, 2026 → Mar 5, 2026

Merge confidence

100%

incident inc_f12d6ef3cf624f9b · merged by human · confidence 100%

Part of the TriZetto Provider Solutions supply-chain incident (2025) — at least 21 organizations filed notifications naming this third party.
Confirmed breach. Merged as one breach: 13 regulatory filings. The filings describe unauthorized access. Intrusion Nov 1, 2024–Oct 2, 2025, discovered Oct 2, 2025 — the first regulatory filing landed 127 days later (flagged late). 3,433,965 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 3 more. Notifications rolled out on a 27-day schedule across 13 filings beginning Feb 6, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
127days

Discovered → first regulatory filing

Discovery variance
57days

Range of discovered_at dates across filings

Filing span
27days

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 >90dTexas✗ TX AG >30dMaine✗ ME AG >90d · 97dHIPAA✓ HHS notifiedSouth Carolina✓ SC CRA notice dueFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Nov 1, 2024breach begins
Oct 2, 2025discovered · members disagree
notification delay · 127 days
Feb 6, 2026first filing
Mar 5, 2026most 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. FEB 6HHS OCRHHS OCR noticefirst filing · states nationwide total 3,433,965day 0
  2. FEB 6MT AGMT AG notice8,072 MT residentsday 0
  3. FEB 6NE AGNE AG noticeno count statedday 0
  4. FEB 6IN AGIN AG noticestates nationwide total 3,433,965day 0
  5. FEB 6VT AGVT AG noticeno count statedday 0
  6. FEB 6WA AGWA AG notice44,985 WA residentsday 0
  7. FEB 6IN AGIN AG noticestates nationwide total 3,433,965day 0
  8. FEB 9TX AGTX AG noticestates nationwide total 3,433,965+3d
  9. FEB 11NH AGNH AG notice1,795 NH residents+5d
  10. FEB 11CA AGCA AG noticeno count stated+5d
  11. FEB 11MA AGMA AG noticeno count stated+5d
  12. FEB 20SC AGSC AG notice3,562 SC residents+14d
  13. MAR 5ME AGME AG noticemost recent · states nationwide total 3,433,965+27d
  14. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 2, 2025
IN AG
Discovered
Oct 2, 2025WA AG + NH AGNov 28, 2025TX AG + ME AGfilings disagree on discovery
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI · PII
HHS OCR + WA AG + TX AG +8
Attack vector
Unauthorized Access
HHS OCR

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)

3,433,965

Sum of filed state slices

237,855· 6.9% of stated

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

US3,433,965
TX171,158
WA44,985
MT8,072
IN7,155
SC3,562
NH1,795
ME1,128

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 Aug 25, 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

27 days

Cadence

~1 / 2.3d

vs. multi-state median

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