Clustered 3 filings across 2 jurisdictions · filing window Dec 4, 2020 → Jan 21, 2021. View entity profile → Other incidents for this victim →
incident inc_92e03cb734944d53 · merge_method human · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
ME MT
Time between earliest and latest filing
Not recorded for this incident
Leak precedence · Materiality delta · SEC filing delay — no leak-site claim in this cluster; no SEC 8-K in this cluster.
all State AG
per-filing reported counts
State AGs report only their own residents; bars show per-filing counts.
Earliest sighting first · deep chronology in Litigation Timeline
Oct 22, 2020
When the intrusion reportedly occurred, per the linked filings
Nov 16, 2020
Reported by MAINE AG filings
American Bank Systems reported a data breach to the Montana Attorney General. The breach was reported on 2020-12-04. The breach occurred on 10/22/2020. 1 Montana residents were affected.
Affected (this filing): 1
American Bank Systems, a commercial entity, experienced an external system breach (hacking) on October 22, 2020, which was discovered on November 16, 2020. The breach affected 21 Maine residents and compromised financial account information. Affected individuals were notified on December 16, 2020, and offered 12 months of credit monitoring from TransUnion.
Affected (this filing): 21
American Bank Systems, a commercial entity, experienced an external system breach (hacking) on October 22, 2020, which was discovered on November 16, 2020. The breach affected 17,092 individuals in total, including one resident of Maine. The compromised information included names or other personal identifiers in combination with Social Security Numbers. Affected individuals were notified in writing on January 21, 2021, and were offered 12 months of one-bureau credit monitoring services from TransUnion.
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.