DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $7.99what’s inside →
Leak SiteHHS OCRState AGConfirmed9 records · 6 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedgroovehigh sensitivity
Merged incident · 9 records

TriValley Primary Care — October 2021 breach

Clustered 9 records across 6 jurisdictions: 8 filings and 1 leak-site claim · filing window Nov 23, 2021 → Jan 10, 2022. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

9 records

States

6

Affected · reported

122,806

First → last filing

Nov 23, 2021 → Jan 10, 2022

Merge confidence

100%

incident inc_9f31f31b6f23461a · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings and 1 unverified claim. Intrusion Oct 11, 2021, discovered Oct 11, 2021 — the first regulatory filing landed 43 days later. 122,806 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), Health (basic), and 2 more. Notifications rolled out on a 48-day schedule across 8 filings beginning Nov 23, 2021. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
43days

Discovered → first regulatory filing

Discovery variance
0days

Range of discovered_at dates across filings

Leak precedence
32days before filing

Days between the first sighting of the earliest-seen leak-site claim and the first regulatory filing. Measured from when the aggregator first saw the post, not the crew's own (often earlier) date. 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
48days

Time between earliest and latest filing

Not recorded for this incident

Materiality delta · SEC filing delay — no SEC 8-K in this cluster.

Regulatory clocksLeak gap⏱ Leak >30dMaine⏱ ME AG >30d · 43dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Oct 11, 2021breach begins
Oct 11, 2021discovered
notification delay · 43 days
Nov 23, 2021first filing
Jan 10, 2022most recent filing

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing and leak-site claim in this incident

  1. OCT 22Leak sitegroove postfirst record · attacker claim · unverifiedday 0
  2. NOV 23MA AGMA AG notice78 MA residents+32d
  3. NOV 23MT AGMT AG notice6 MT residents+32d
  4. NOV 23ME AGME AG noticestates nationwide total 57,596+32d
  5. NOV 23HHS OCRHHS OCR noticestates nationwide total 122,806+32d
  6. NOV 24IN AGIN AG noticestates nationwide total 57,596+33d
  7. NOV 29NH AGNH AG notice11 NH residents+38d
  8. JAN 6ME AGME AG noticestates nationwide total 122,806+76d
  9. JAN 10NH AGNH AG noticemost recent · 29 NH residents+80d
  10. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Oct 11, 2021
ME AG
Discovered
Oct 11, 2021
MT AG + ME AG + NH AG
Data types
Financial account · Health (basic) · Identity (basic) · Government ID · PHI
MA AG + MT AG + ME AG +2
Attack vector
Ransomware
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)

122,806

Sum of filed state slices

142· 0.1% of stated

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

US122,806
MA78
NH29
IN19
ME10
MT6

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

48 days

Cadence

~1 / 6.9d

vs. multi-state median

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