Amotec, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2023-02-10. The breach occurred from 12/26/2022 to 1/23/2023. 1 Montana residents were affected.
Affected (this filing): 1
Clustered 2 filings across 2 jurisdictions · filing window Feb 10, 2023 → Feb 14, 2023. View entity profile → Other incidents for this victim →
incident inc_c944e8361ac448c4 · 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
Dec 26, 2022
When the intrusion reportedly occurred, per the linked filings
Dec 26, 2022
Reported by NEW HAMPSHIRE AG filing
Amotec, Inc. reported a data breach to the Montana Attorney General. The breach was reported on 2023-02-10. The breach occurred from 12/26/2022 to 1/23/2023. 1 Montana residents were affected.
Affected (this filing): 1
Amotec, Inc. notified the New Hampshire Attorney General of a data event affecting 10 NH residents. On December 26, 2022, suspicious activity was discovered, leading to the determination that an unknown actor accessed systems and potentially acquired files containing names, SSNs, driver's license numbers, and financial account information. Amotec engaged forensic specialists, notified law enforcement, and provided 12 months of credit monitoring to affected individuals.
Affected (this filing): 10
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.