Clustered 2 filings across 2 jurisdictions · filed Apr 26, 2024. View entity profile → Other incidents for this victim →
incident inc_7a1aa839e1b94ab3 · 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.
Government ID · Identity (basic)
MA ME
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Sep 13, 2023
When the intrusion reportedly occurred, per the linked filings
Feb 26, 2024
Reported by MAINE AG filing
Aspire Health Alliance reported to HHS on 2024-04-26 a Hacking/IT Incident affecting 17,490 individuals. Breached information located on Network Server. The incident involved a ransomware attack encrypting PHI (including names, DOB, SSN, driver's license, and financial data). The entity offered credit monitoring and implemented security safeguards.
Affected (this filing): 17,490
Aspire Health Alliance, a healthcare entity based in Braintree, MA, experienced an external system breach (hacking) on September 13, 2023. The incident was discovered on February 26, 2024, affecting 17,490 individuals, including 22 Maine residents. The breach compromised names and Social Security Numbers. Aspire Health Alliance notified affected individuals in writing on April 26, 2024, and offered 12 months of credit and dark web monitoring, along with identity theft recovery services.
Affected (this filing): 17,490
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.