DisclosureLens
All incidentsView linkage analytics →Get the evidence package — $79
State AGConfirmed1 filing · 1 stateLifecycle stage 2 of 3: ConfirmedUnverified claimConfirmedEnforcedlow sensitivity
Incident · single filing

CITIZENS BANK — March 2025 breach

One linked filing — more sources may join as they report · filed Mar 28, 2025. View entity profile → Other incidents for this victim →

Determination

Confirmed

Members

1 filing

States

1

Affected · reported

12

First → last filing

Mar 28, 2025

incident inc_fe0b675a4c0d43a4 · merged by deterministic

Confirmed breach. Intrusion Mar 4, 2025, discovered Mar 6, 2025 — the first regulatory filing landed 22 days later. 12 individuals reported across the linked filings.

Litigation Timing

Notification delay
22days

Discovered → first regulatory filing

Not recorded for this incident

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 clocksMaine✓ ME AG ≤30d · 22dFull clock table in Litigation Timeline

Incident timeline

Mar 4, 2025breach begins
Mar 6, 2025discovered
notification delay · 22 days
Mar 28, 2025first & only filing
—watching for filings

Dashed segments are unestablished, not zero — they fill in as filings merge into this incident.

Member cascade — every filing about this breach

  1. MAR 28ME AGME AG noticeonly filing · states nationwide total 12day 0
  2. Watching for additional filings — new sources merge into this incident automatically.

Roll-up facts — reconciled across members

Breach window
Mar 4, 2025
ME AG
Discovered
Mar 6, 2025· 2d undetected
ME AG
Data types
PII
ME AG
Attack vector
Insider
ME AG
Response
Written notification sent to affected Maine residents on 03/27/2025 · Two-year identity theft credit monitoring service (myTrueIdentity) offered via TransUnion Interactive
ME AG

Each fact cites the member filing that establishes it; when filings conflict, every value shows with its source.

Count reconciliation

per-state reported counts

Nationwide (stated in a filing)

12

Sum of filed state slices

1· 8.3% of stated

92% of the stated total lives in states whose filings carry no count — the dashed share shrinks as filings land.

Evidence ladder — rungs this incident occupies

Leak-site claim

No leak-site claim on record for this incident.

Press / market report

No press coverage linked yet.

State AG / regulator filing1 member

Unlocks: discovery date, data types, affected count, compliance clock.

SEC 8-K / victim statement

No SEC filing or victim statement yet.

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.