Clustered 4 filings across 3 jurisdictions · filing window Nov 19, 2024 → Jan 30, 2026. View entity profile → Other incidents for this victim →
incident inc_bc9a9f6def5740cd · merge_method human · confidence 100%
Discovered → first regulatory filing
Gap between first leak claim and first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Materiality delta · SEC filing delay — no SEC 8-K in this cluster; needs two dated filings.
IN NH
Leak Site · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 19, 2024
When the intrusion reportedly occurred, per the linked filings
Nov 19, 2024
Reported by NEW HAMPSHIRE AG filing
Alpine ENT is committed to providing comprehensive, high-quality ear, nose and throat care to the entire family through all stages of life.
Alpine ENT is committed to providing comprehensive, high-quality ear, nose and throat care to the entire family through all stages of life.
Alpine Ear Nose and Throat reported a data breach to the Indiana Attorney General. The breach occurred on 2024-11-19 and was reported on 2026-01-30. 18 Indiana residents were affected. 65,648 individuals affected in total.
Alpine Ear, Nose, & Throat, P.C. (AENT) notified the New Hampshire Attorney General of a cybersecurity incident discovered on November 19, 2024. The breach potentially exposed personal, medical, and financial data of 65,648 individuals, including 8 New Hampshire residents. AENT engaged forensic investigators and an MSP, offered 12 months of credit monitoring, and enhanced technical security measures. Notification letters were mailed on January 30, 2026.
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.
Affected (this filing): 65,648
Affected (this filing): 65,648