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

Confirmed10 filings · 8 statesUnverified claimConfirmedEnforcedhigh sensitivity

Merged incident · 10 filings

Aspire Rural Health System — November 2024 breach

Clustered 10 filings across 9 jurisdictions · filing window Jan 6, 2025 → Aug 25, 2025. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

10 filings

States

Affected · reported

138,386

First → last filing

Jan 6, 2025 → Aug 25, 2025

Merge confidence

100%

incident inc_fa250bc5bcd0422f · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 8 regulatory filings and 2 unverified claims. The filings describe unauthorized access. Intrusion Nov 4, 2024–Jan 6, 2025, discovered Nov 4, 2024 — the first regulatory filing landed 289 days later (flagged late). 138,386 individuals reported across the linked filings. Data reported: Government ID, Identity (basic), PHI, and 2 more. Notifications rolled out on a 231-day schedule across 8 filings beginning Jan 6, 2025. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental

Notification delay

289days

Discovered → first regulatory filing

Discovery variance

256days

Range of discovered_at dates across filings

Leak precedence

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

231days

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

Sensitive data

identity_government

Incident timeline

Nov 4, 2024breach begins

Nov 4, 2024discovered · members disagree

notification delay · 289 days

Aug 20, 2025first filing

Aug 25, 2025most recent filing

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

Member cascade — every filing about this breach

JAN 6Leak sitebianlian postfirst filing · attacker claim · unverifiedoperator-confirmedday 0
FEB 13Leak sitebianlian postattacker claim · unverifiedoperator-confirmed+39d
AUG 20VT AGVT AG noticeno count statedoperator-confirmed+226d
AUG 20IN AGIN AG noticestates nationwide total 138,386operator-confirmed+226d
AUG 20HHS OCRHHS OCR noticestates nationwide total 138,386operator-confirmed+226d
AUG 20NE AGNE AG noticeno count statedauto-linked+226d
AUG 21MA AGMA AG notice28 MA residentsoperator-confirmed+227d
AUG 21ME AGME AG noticestates nationwide total 138,386operator-confirmed+227d
AUG 22TX AGTX AG noticestates nationwide total 138,386operator-confirmed+228d
AUG 25NH AGNH AG noticemost recent · 3 NH residentsoperator-confirmed+231d
Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window: Nov 4, 2024 – Jan 6, 2025
Discovered: Nov 4, 2024NE AGJul 18, 2025ME AG + TX AG + NH AGfilings disagree on discovery
Data types: Health (basic) · Identity (basic) · Government ID · PHI · PII
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)

138,386

Sum of filed state slices

581· 0.4% of stated

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

US138,386

TX477

IN69

MA28

ME4

NH3

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

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

231 days

Cadence

~1 / 25.7d

vs. multi-state median

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