Bank3
bd_3df0f61142e3ee2c · schema v1 · pii pii-v1
Full breach record for Bank3 →Threat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Qilin 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
Bank3, USA - it's a disaster for the clients. Bank3 is a community-driven banking institution offering personal and business banking services, as well as mortgage lending. The bank serves clients in various locations including Memphis, Nashvi ...
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Oct 13, 2025
Claim posted
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Claim → filing
—
Compliance clock
Not assessable
Linked disclosures
Why this link?Ransomware claims (1)
- Leak Siteqilinbd_a70798c645cca2222025-08-07 · +67dVerified
Regulatory filings (6) · sorted by filing gap
- Massachusetts State AGbd_4d9a6c6fd7f188af2026-04-15 · +184dVerified by operator
- Indiana State AGbd_62c2cbbc97c93fe32026-04-15 · +184dVerified
- Nebraska State AGbd_a025bf374ab24d892026-04-15 · +184dVerified
- New Hampshire State AGbd_d533cd30fb221b4f2026-04-15 · +184dVerified
Show 2 more filings ↓Show fewer ↑up to 186d gap
- Maine State AGbd_d9e32011b79615912026-04-15 · +184dVerified
- Texas State AGbd_3bffe71b571f10052026-04-17 · +186dVerified
Filing propagation · 7 filings · 6 states
View merged incident ↗Pattern: first filing Oct 13, last Apr 17 (TX) — a 186-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.
qilin
According to ransomware.live, Qilin ransomware was first observed in July of 2022. Qilin Ransomware is written in Golang and supports multiple encryption modes; all of which are controlled by the operator. Qilin actors practice double extortion – demanding payment for a decryptor, as well as for the non-release of stolen data.