Confirmed breach. Intrusion Jan 10, 2024–Jun 13, 2024, discovered Jul 10, 2024 — the first regulatory filing landed 78 days later (flagged late). 100 individuals reported across the linked filings.
Discovery variance · Leak precedence · Materiality delta · SEC filing delay · Filing span — no leak-site claim in this cluster; no SEC 8-K in this cluster; needs two dated filings.
Regulatory clocksVermont✗ VT AG >45 bdayFull clock table in Litigation Timeline
State AGConfirmedLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedhigh sensitivity
Affected (total reported)
100
Data types
3
Identity (basic) · Government ID · Financial account
Jurisdictions
1
VT
Linked filings
1
all State AG
Sensitive data
identity_government
Timeline
Earliest sighting first · deep chronology in Litigation Timeline
Breach window
Jan 10, 2024 → Jun 13, 2024
When the intrusion reportedly occurred, per the linked filings
Citizens Bank notified Vermont AG on 2024-09-26 of an incident where images containing customer PII (name, SSN, account number) were shared with an unauthorized party between Jan-Jun 2024. ~100 customers affected. Bank offered 2 years of TransUnion credit monitoring.
Affected (this filing): 100
VT AG >45 bday
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.