Eastern Bank
bd_f59acb674bba6daf · schema v1 · pii pii-v1
Full breach record for Eastern Bank →204 incidents on fileEastern Bank notified Massachusetts customers on May 13, 2026, that a merchant accepting Eastern Bank Debit MasterCard BusinessCards experienced a security breach. The bank could not obtain details from the merchant. Eastern Bank took proactive measures including lowering card limits to $500 and issuing new debit cards to affected customers. Customers were instructed to activate new cards, destroy old ones, and monitor accounts for suspicious activity. No specific data types or counts were disclosed.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
May 13, 2026
Filed
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Linked disclosures
Why this link?Regulatory filings (3) · sorted by filing gap
- Massachusetts State AGbd_566f14d500ef34f32026-06-30 · +48dCandidate
- Massachusetts State AGbd_d9eac86bf9dbdfd72026-07-24 · +72dCandidate
- Massachusetts State AGbd_682592668a83450f2026-08-06 · +85dCandidate
Filing propagation · 4 filings
View merged incident ↗Pattern: first filing May 13 (MA), last Aug 6 (MA) — a 85-day rolling notification. Rolling spreads often mean counsel is filing as thresholds trip per state. Why this link?
Evidence ladder
Attacker assertion only. Establishes: claim date, group, alleged victim.
Unlocks: incident narrative, operational impact. Still no compliance clock.
Unlocks: discovery date, data types, affected count, compliance clock.
Unlocks: materiality, stated response, full audit trail. Ceiling removed.