Sawyer Savings Bank
bd_85058926155265b1 · schema v1 · pii pii-v1
Full breach record for Sawyer Savings Bank →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Storm on its public extortion blog. It has not been validated by the victim or any regulator. Treat attribution and counts as the threat actor's assertion until a regulatory filing or victim disclosure corroborates them.
Source: Ransomware.live
Post text · scraped from the leak site
Sawyer Savings Bank is a community-focused financial institution with over 150 years of experience, offering a range of personal and business banking services. Their products include personal checking, savings accounts, business loans, and digital banking solutions designed to enhance customer convenience and security. The bank is dedicated to supporting local communities through various initiatives, including scholarships and volunteerism. Their target clients include individuals seeking personal banking solutions and businesses looking for comprehensive banking support. The company headquarters is located in 87 Market Street, Saugerties, NY 12477, United States.11-50 Employees
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Aug 7, 2026
Claim posted
—
Corroborated · see linked filings
This record's own dates cannot anchor compliance clocks; see the linked filings.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Regulatory filings (2) · sorted by filing gap
- Massachusetts State AGbd_f046e49f12f786b32026-10-01 · +55dCandidate
- Vermont State AGbd_132791e2319a6e8f2026-10-09 · +63dVerified by operator
Press reports (1)
- PressStormbd_648aab30115eda852026-08-03 · +4dCandidate
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
- actor name
- victim claim
- ransom/leak status
- discovery date
- materiality
- notification
- affected count
- confirmed data types
- compliance clock
The ✕ fields stay blank until a regulatory filing or victim disclosure lands.