Cadence Bank
bd_904e886fa624bb04 · schema v1 · pii pii-v1
Full breach record for Cadence Bank →3 incidents on fileThreat-actor claim — not a regulatory filing
This row is a claim by the ransomware group Cl0p 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
Cadence Bank - Home
J jump to incidentP pin to compareR raw source
Incident timeline — mostly unverified
? — ?
Breach window unknown
Jul 6, 2023
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 Sitedispossessorbd_955b68cfd2f4b2942024-04-19 · +288dVerified by operator
Regulatory filings (5) · sorted by filing gap
- California State AGbd_3a402a6f99ec3ecc2023-09-15 · +71dVerified by operator
- Vermont State AGbd_9eeb910d8c5188af2023-09-15 · +71dVerified by operator
- Massachusetts State AGbd_b9c2b0baae525a492023-09-15 · +71dVerified by operator
- Montana State AGbd_d1a549216a802d0f2023-09-15 · +71dVerified by operator
Show 1 more filing ↓Show fewer ↑up to 204d gap
- California State AGbd_967842f4b2ee04d22024-01-26 · +204dVerified
Filing propagation · 6 filings · 4 states
View merged incident ↗Pattern: first filing Jul 6, last Jan 26 (CA) — a 204-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.