Clustered 3 filings across 3 jurisdictions · filed Mar 24, 2023. View entity profile → Other incidents for this victim →
incident inc_57ba3c82d6a4464f · 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.
Identity (basic) · Government ID
ME MT TX
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Nov 10, 2022 → Nov 27, 2022
When the intrusion reportedly occurred, per the linked filings
Jan 24, 2023
Reported by MAINE AG filing
American Pain and Wellness, PLLC reported to HHS on 2023-03-24 a Hacking/IT Incident affecting 7457 individuals. Breached information located on Network Server. The incident involved a ransomware attack encrypting PHI including names, SSNs, addresses, DOB, diagnoses, lab results, and medications. The entity provided credit monitoring and implemented safeguards.
Affected (this filing): 7,457
American Pain and Wellness, a healthcare organization, experienced an external system breach (hacking) that occurred between November 10, 2022, and November 27, 2022. The breach was discovered on January 24, 2023. The compromised information includes names and Social Security numbers. One Maine resident was affected out of a total of 7,457 individuals. Consumers were notified in writing on March 24, 2023. Identity theft protection services were not offered.
Affected (this filing): 1
American Pain & Wellness reported a data breach to the Montana Attorney General. The breach was reported on 2023-03-24. The breach occurred from 11/10/2022 to 11/27/2022. 4 Montana residents were affected.
Affected (this filing): 4
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.