DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79what’s inside →
State AGConfirmed5 filings · 5 statesLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Merged incident · 5 filings

Gila Health Resources, LLC — December 2025 breach

Clustered 5 filings across 5 jurisdictions · filing window Aug 1, 2026 → Aug 10, 2026. View entity profile → Other incidents for this victim →

⚠ 2 cross-filing discrepancies →Merge100%

Determination

Confirmed

Members

5 filings

States

5

Affected · reported

1,164

First → last filing

Aug 1, 2026 → Aug 10, 2026

Merge confidence

100%

incident inc_c3f27eec417f4258 · merged by deterministic · confidence 100%

Confirmed breach. Merged as one breach: 5 regulatory filings. The filings describe unauthorized access. Intrusion Dec 2, 2025–Dec 18, 2025, discovered Dec 18, 2025 — the first regulatory filing landed 226 days later (flagged late). 1,164 individuals reported across the linked filings. Data reported: Government ID, Health (basic), PHI, and 1 more. Notifications rolled out on a 9-day schedule across 5 filings beginning Aug 1, 2026. Each member filing remains the legal record for its jurisdiction.

Litigation Timing

Supplemental
Notification delay
226days

Discovered → first regulatory filing

Discovery variance
230days

Range of discovered_at dates across filings

Filing span
9days

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 clocksMassachusetts✗ MA AG >90dTexas✓ TX AG ≤30dFull clock table in Litigation Timeline

Sensitive data

identity_government

Incident timeline

Dec 2, 2025breach begins
Dec 18, 2025discovered · members disagree
notification delay · 226 days
Aug 1, 2026first filing
Aug 10, 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. AUG 1IL AGIL AG noticefirst filing · no count statedday 0
  2. AUG 7MA AGMA AG notice6 MA residents+6d
  3. AUG 7NE AGNE AG noticeno count stated+6d
  4. AUG 7VT AGVT AG notice1 VT residents+6d
  5. AUG 10TX AGTX AG noticemost recent · 1,157 affected+9d
  6. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Dec 2, 2025 – Dec 18, 2025
MA AG
Discovered
Dec 18, 2025MA AG + NE AGAug 5, 2026IL AG + TX AGfilings disagree on discovery
Data types
Health (basic) · Identity (basic) · Government ID · PHI
IL AG + NE AG + TX AG +2
Attack vector
Unauthorized Access
MA AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Affected residents by state

per-state reported counts

TX1,157
MA6
VT1

State AGs report only their own residents; teal bars show each state's reported slice.

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

9 days

Cadence

~1 / 2.3d

vs. multi-state median

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