← River Financial Corporation

2026 River Financial / River Bank & Trust — ransomware; data exfil; actor claims deletion (SEC 8-K)

2026 Unknown records affected Share on X

Data compromised

Personally identifiable information exposure under investigation; certain operations impacted; full scope not determined at June 25, 2026 filing

Technical writeup

Verified SEC cybersecurity disclosure — June 25, 2026. River Financial Corporation, holding company for River Bank & Trust in Prattville, Alabama, filed Form 8-K Item 1.05 reporting that on or about June 16, 2026 an unauthorized threat actor gained access to its network environment, including River Bank & Trust systems. River identified the activity on or about June 19, 2026 and determined ransomware had been deployed across portions of its server environment. The bank took containment measures including disabling affected administrative accounts and taking impacted systems offline. With third-party forensics, River was investigating whether personally identifiable information was subject to unauthorized access or exfiltration; as of the filing date the full nature, scope, and impact had not been determined and certain operations were impacted while restoration continued. River stated it would amend the 8-K within four business days after material scope information became available. BreachHistory indexes recordsAffected 0 pending victim-count disclosure. SecurityWeek later coverage: subsequent SEC 8-Ks state hackers accessed portions of the network and exfiltrated certain data; at least four lawsuits filed. River said it obtained representations from the threat actor that stolen data in the actor’s possession was deleted (wording consistent with ransom/suppression engagement). Company still had not confirmed whether the incident is reasonably likely to materially impact business/financial condition, and PII scope remained under investigation in filings reviewed.

Root cause

Unauthorized threat actor accessed network ~June 16, 2026; ransomware deployed; discovered ~June 19 per SEC Item 1.05 filing

References