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

Confirmed5 records · 4 statesUnverified claimConfirmedEnforcedalphvhigh sensitivity

Merged incident · 5 records

Jewish Home Lifecare — January 2024 breach

Clustered 5 records across 4 jurisdictions: 4 filings and 1 leak-site claim · filing window Mar 8, 2024 → Aug 16, 2024. View entity profile → Other incidents for this victim →

⚠ 1 cross-filing discrepancy →Merge100%

Determination

Confirmed

Members

5 records

States

Affected · reported

104,234

First → last filing

Mar 8, 2024 → Aug 16, 2024

Merge confidence

100%

incident inc_a5b82794b5d849df · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 4 regulatory filings and 1 unverified claim. The filings describe unauthorized access. Intrusion Jan 7, 2024, discovered Jan 7, 2024 — the first regulatory filing landed 61 days later; 1 later filing was flagged late. 104,234 individuals reported across the linked filings. Data reported: Government ID, PHI, Health (basic), and 2 more. Notifications rolled out on a 161-day schedule across 4 filings beginning Mar 8, 2024. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

61days

Discovered → first regulatory filing

Discovery variance

0days

Range of discovered_at dates across filings

Leak precedence

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

161days

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 >180dVermont✗ VT AG >45 bdayHIPAA✓ HHS notifiedFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Jan 7, 2024breach begins

Jan 7, 2024discovered

notification delay · 61 days

Mar 8, 2024first filing

Aug 16, 2024most 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

FEB 8Leak sitealphv postfirst record · attacker claim · unverifiedoperator-confirmedday 0
MAR 8HHS OCRHHS OCR noticestates nationwide total 104,234auto-linked+28d
AUG 16MA AGMA AG notice198 MA residentsoperator-confirmed+189d
AUG 16ME AGME AG noticestates nationwide total 104,234auto-linked+189d
AUG 16VT AGVT AG noticemost recent · no count statedoperator-confirmed+189d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Jan 7, 2024
Discovered: Jan 7, 2024
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)

104,234

Sum of filed state slices

220· 0.2% 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 claim1 member

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

Press / market report

No press coverage linked yet.

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

161 days

Cadence

~1 / 53.7d

vs. multi-state median

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