Sawyer Savings Bank
bd_648aab30115eda85 · schema v1 · pii pii-v1
Full breach record for Sawyer Savings Bank →Press / market disclosure — not a breach-notification filing
A media or market posting that confirms an incident but carries no breach-notification fields, so compliance clocks aren't assessable. The summary below is extracted from the coverage — verify against the source.
Sawyer Savings Bank of New York keeps branches closed amid possible data security incident. Sawyer Savings Bank: Sawyer Savings Bank had to close its New York branches following a network disruption related to a data security incident involving a vulnerability at one of its suppliers. The incident began on Monday, August 3, and although digital banking services (ATMs, online banking) remained operational, the bank stated that no evidence has been found so far regarding compromise of customer accounts. The investigation into the nature and extent of the incident is ongoing. Linked ransomware group: Storm.
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Aug 3, 2026
Press report
—
Corroborated · see linked filings
This record's own dates cannot anchor compliance clocks; see the linked filings.
Attack → press
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Sitestormbd_85058926155265b12026-08-07 · +4dCandidate
Regulatory filings (2) · sorted by filing gap
- Massachusetts State AGbd_f046e49f12f786b32026-10-01 · +59dCandidate
- Vermont State AGbd_132791e2319a6e8f2026-10-09 · +67dVerified by operator
Filing propagation · 2 filings · 2 states
View merged incident ↗Pattern: first filing Oct 1 (MA), last Oct 9 (VT) — a 8-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.
Source ceiling
- incident type + narrative only (may be machine-translated)
- discovery date
- materiality
- affected count
- data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.