Nonstop Administration and Insurance Services, Inc reported a data breach to the Montana Attorney General. The breach was reported on 2023-03-14. The breach occurred on 12/22/2022. 2 Montana residents were affected.
Affected (this filing): 2
Clustered 2 filings across 2 jurisdictions · filing window Mar 14, 2023 → Mar 27, 2023. View entity profile → Other incidents for this victim →
incident inc_475abb65498341ec · merge_method deterministic · confidence 100%
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.
Health (basic) · Identity (basic) · Government ID
MT PA
HHS OCR · State AG
Earliest sighting first · deep chronology in Litigation Timeline
Dec 22, 2022
When the intrusion reportedly occurred, per the linked filings
Nonstop Administration and Insurance Services, Inc reported a data breach to the Montana Attorney General. The breach was reported on 2023-03-14. The breach occurred on 12/22/2022. 2 Montana residents were affected.
Affected (this filing): 2
Nonstop Administration and Insurance Services, Inc. (a Business Associate, PA) reported to HHS OCR on 2023-03-27 a Hacking/IT Incident (cyber-attack) affecting 10,504 individuals. PHI on a Network Server was compromised, including names, gender, addresses, email addresses, phone numbers, dates of birth, Social Security numbers, diagnoses, claims, financial information, and health insurance/treatment information. The BA and covered entity notified affected individuals. Mitigation included enhanced administrative, technical, and security safeguards.
Affected (this filing):
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.