River Financial Corporation
bd_712200f8a5f0b33a · schema v1 · pii pii-v1
Full breach record for River Financial Corporation →River Financial Corporation filed a supplemental 8-K regarding a cybersecurity incident. The company states it has reason to believe certain data was potentially impacted but has not yet confirmed the nature, scope, or whether PII was affected. No evidence of account impact exists. The full impact is undetermined, and the company plans to file an amendment within four business days after determining the information is available.
J jump to incidentP pin to compareR raw source
Incident timeline — partial
? — ?
Breach window unknown
Jul 6, 2026
Filed
—
Corroborated · see linked filings
Compliance clocks stay unassessable until a regulatory filing lands. Dashed segments fill in automatically when corroboration arrives.
Linked disclosures
Why this link?Regulatory filings (4) · sorted by filing gap
- SEC 8-Kbd_5003c9d941db0a9c2026-07-10 · +4dVerified by operator
- SEC 8-Kbd_994819586d228b3b2026-07-17 · +11dVerified by operator
- SEC 8-Kbd_b49f2a1e760cb3ea2026-06-25 · +11dCandidate
- SEC 8-Kbd_a605d6d2312874f32026-07-30 · +24dVerified
Filing propagation · 5 filings
View merged incident ↗Pattern: first filing Jun 25, last Jul 30 — a 35-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.