Clustered 3 filings across 3 jurisdictions · filed Jun 21, 2024. View entity profile → Other incidents for this victim →
incident inc_2bbfe2ec00bb46b8 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Time between earliest and latest filing
Not recorded for this incident
Discovery variance · Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
ME MT PA
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Mar 8, 2024
When the intrusion reportedly occurred, per the linked filings
Apr 23, 2024
Reported by MAINE AG filing
Altoona Logan Township Mobile Medical Emergency Department Authority reported a data breach to the Montana Attorney General. The breach was reported on 2024-06-21. The breach occurred from 3/8/2024 to 3/12/2024. 1 Montana residents were affected.
Affected (this filing): 1
Altoona Logan Township Mobile Medical Emergency Department Authority reported to HHS on 2024-06-21 a Hacking/IT Incident affecting 6,169 individuals. Breached information located on Network Server. The cyberattack compromised PHI including names, DOB, addresses, and phone numbers. The entity provided credit monitoring and implemented additional safeguards.
Affected (this filing): 6,169
Altoona Logan Township Mobile Medical Emergency Department Authority, a government entity in the healthcare sector, reported an external system breach (hacking) that occurred between March 8, 2024, and March 12, 2024. The breach was discovered on April 23, 2024. The incident affected 2 Maine residents, who were notified on June 21, 2024. The company offered 12 months of identity theft protection services through CyEx.
Affected (this filing): 2
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.