Confirmed breach. Intrusion Feb 25, 2026, discovered Feb 25, 2026 — the first regulatory filing landed 65 days later. 35,632 individuals reported across the linked filings.
Gastro Health disclosed a phishing incident on February 25, 2026, resulting in unauthorized access to patient files. Affected data included names, SSNs, DOBs, state IDs, medical record numbers, and financial account numbers. The incident is contained, with no indication of fraud. Gastro Health provided 24 months of credit monitoring via Epiq Privacy Solutions.
MA AG >30d
🏎️Indiana State AGlinked via same-victim cross-source · 100%
Gastro Health reported a data breach to the Indiana Attorney General. The breach occurred on 2026-02-25 and was reported on 2026-05-22. 55 Indiana residents were affected. 35,632 individuals affected in total.
Affected (this filing): 35,632
🇺🇸FLHHS OCRlinked via same-victim cross-source · 100%
Gastro Health notified the New Hampshire Attorney General of a phishing incident affecting approximately 35 NH residents. The breach occurred on February 25, 2026, when employee credentials were compromised via a malicious email. Gastro Health contained the incident by disabling accounts and resetting passwords. Affected data included names, SSNs, DOBs, and protected health information. Notifications were sent on May 22, 2026, offering 24 months of credit monitoring.
Affected (this filing): 35
🌲Washington State AGMost recentlinked via multistate filing link · 95%
Gastro Health, a health sector entity reported a unauthorized access incident to the Washington Attorney General. The organization became aware of the incident on 2026-02-25 and filed notice on 2026-05-22. 1,813 Washington residents were affected. 86 days elapsed between awareness and notification. 1 days to identify the breach. 0 days to contain the breach.
Affected (this filing): 1,813
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. Filing summaries shown in the timeline are AI-generated extracts — verify each against its linked source.