Savers Co-operative Bank
bd_bc33f8b8ed9a4c39 · schema v1 · pii pii-v2
Full breach record for Savers Co-operative Bank →345 incidents on fileSavers Bank notified customers that a suspected security breach of a third-party merchant's network may have compromised some debit card numbers. No fraudulent activity was observed. The bank is reissuing affected cards and deactivating old ones. Customers are advised to monitor accounts and review credit reports.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Aug 1, 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 (6) · sorted by filing gap
- Massachusetts State AGbd_360e966706824cce2026-07-23 · +9dCandidate
- Massachusetts State AGbd_4fb676c0d44bf70c2026-07-21 · +11dCandidate
- Massachusetts State AGbd_26348f2f1df491e52026-06-23 · +39dCandidate
- Massachusetts State AGbd_8a5b6fb6fa2acacc2026-06-23 · +39dCandidate
Show 2 more filings ↓Show fewer ↑up to 85d gap
- Massachusetts State AGbd_bbf621a605a3c8b32026-06-23 · +39dCandidate
- Massachusetts State AGbd_552579c934e54be62026-05-08 · +85dCandidate
Filing propagation · 7 filings
View merged incident ↗Pattern: first filing May 8 (MA), last Aug 1 (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.