All incidents View linkage analytics →Get the evidence package — $79 what’s inside →

Confirmed7 filings · 4 statesUnverified claimConfirmedEnforcedbianlianhigh sensitivity

Merged incident · 7 filings

Hypertension Nephrology Associates, P.C. — January 2024 breach

Clustered 7 filings across 5 jurisdictions · filing window Feb 6, 2024 → May 24, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

7 filings

States

Affected · reported

39,491

First → last filing

Feb 6, 2024 → May 24, 2024

Merge confidence

100%

incident inc_24b7c1694cea4ea0 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings, 1 press report and 2 unverified claims. The filings describe malware. Intrusion Jan 20, 2024–Feb 6, 2024, discovered Feb 6, 2024 — the first regulatory filing landed 85 days later. 39,491 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 2 more. Notifications rolled out on a 108-day schedule across 4 filings beginning Feb 6, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

85days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Leak precedence

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

108days

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 >30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 20, 2024breach begins

Feb 6, 2024discovered

notification delay · 85 days

May 1, 2024first filing

May 24, 2024most recent filing

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

Member cascade — every filing about this breach

FEB 6Leak sitebianlian postfirst filing · attacker claim · unverifiedoperator-confirmedday 0
FEB 28Leak sitebianlian postattacker claim · unverifiedoperator-confirmed+23d
MAY 1IL AGIL AG noticeno count stated+85d
MAY 14HHS OCRHHS OCR noticestates nationwide total 39,491auto-linked+98d
MAY 24MA AGMA AG notice16 MA residentsauto-linked+108d
MAY 24MT AGMT AG noticemost recent · 2 MT residentsauto-linked+108d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Jan 20, 2024 – Feb 6, 2024
Discovered: Feb 6, 2024· 17d undetected
Data types: Financial account · Health (basic) · Identity (basic) · Government ID · PHI
Attack vector: Unauthorized Access

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)

39,491

Sum of filed state slices

18· 0.0% of stated

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

Evidence ladder — rungs this incident occupies

Leak-site claim2 members

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

Press / market report1 member

Unlocks: incident narrative, operational impact. Still no compliance clock.

State AG / regulator filing4 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

108 days

Cadence

~1 / 18d

vs. multi-state median

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