AlohaCare reported a data breach to the Montana Attorney General. The breach was reported on 2023-11-03. The breach occurred from 5/29/2023 to 5/31/2023. 32 Montana residents were affected.
Affected (this filing): 32
Clustered 2 filings across 2 jurisdictions · filed Nov 3, 2023. View entity profile → Other incidents for this victim →
incident inc_c9e6ee0cc3624653 · 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.
MT NH
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 29, 2023
When the intrusion reportedly occurred, per the linked filings
May 31, 2023
Reported by NEW HAMPSHIRE AG filing
AlohaCare reported a data breach to the Montana Attorney General. The breach was reported on 2023-11-03. The breach occurred from 5/29/2023 to 5/31/2023. 32 Montana residents were affected.
Affected (this filing): 32
AlohaCare, a Hawaii-based health insurance provider, notified the New Hampshire Attorney General on November 3, 2023, of a data security incident involving the MOVEit file transfer tool vulnerability. The incident, discovered on or around May 31, 2023, impacted 12 New Hampshire residents. The breach exposed personal and protected health information. AlohaCare engaged third-party experts, notified credit bureaus, and offered complimentary credit monitoring and identity theft recovery services to affected individuals.
Affected (this filing): 12
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.