Clustered 2 filings across 2 jurisdictions · filing window Jun 2, 2023 → Jun 7, 2023. View entity profile → Other incidents for this victim →
incident inc_d794752c9edd4359 · merge_method deterministic · confidence 100%
Discovered → first regulatory filing
Range of discovered_at dates across filings
Identity (basic) · Financial account
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.
ME VT
all State AG
Earliest sighting first · deep chronology in Litigation Timeline
May 12, 2023
When the intrusion reportedly occurred, per the linked filings
May 12, 2023
Reported by VERMONT AG, MAINE AG filings
KeyBank notified Vermont consumers of a security incident occurring on or about May 12, 2023, where unauthorized actors used personal information to create online banking profiles. Affected data included names, SSNs, financial account numbers, and transaction history. KeyBank engaged law enforcement and forensic experts, and offered two years of Equifax credit monitoring.
KeyBank, a financial services company, reported a data breach affecting 3 Maine residents. The breach was attributed to insider wrongdoing and was discovered on May 12, 2023, the same day it occurred. The compromised information includes names in combination with financial account numbers or credit/debit card numbers and their associated access codes. KeyBank notified the affected individuals on June 7, 2023, and offered two years of credit monitoring and identity theft protection services through Equifax.
Affected (this filing): 3
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.