North American Rescue reported a data breach to the Montana Attorney General. The breach was reported on 2022-06-09. The breach occurred from 4/2/2022 to 4/28/2022. 30 Montana residents were affected.
Affected (this filing): 30
Clustered 2 filings across 2 jurisdictions · filing window Jun 9, 2022 → Jun 11, 2022. View entity profile → Other incidents for this victim →
incident inc_e5c5403a666e4eac · 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
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
Apr 2, 2022
When the intrusion reportedly occurred, per the linked filings
Apr 28, 2022
Reported by MAINE AG filing
North American Rescue reported a data breach to the Montana Attorney General. The breach was reported on 2022-06-09. The breach occurred from 4/2/2022 to 4/28/2022. 30 Montana residents were affected.
Affected (this filing): 30
North American Rescue, LLC reported an external system breach (hacking) occurring between April 2 and April 28, 2022. The incident compromised the personal information and financial account numbers (including credit/debit card numbers with security codes or PINs) of 3,168 individuals, including 15 Maine residents. The breach was discovered on April 28, 2022. The company provided written notification to affected individuals on June 9, 2022, and offered 24 months of identity theft protection services through Experian.
Affected (this filing): 3,168
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.