Skip to content
cisonews.net

Incident · 8-K Item 1.05

River Financial ransomware attack: what River Bank & Trust's parent told the SEC, and how it responded

Compiled from public records. Updated 2026-11-07. By the cisonews.net Desk.

River Financial Corporation, the parent of River Bank & Trust, told the SEC in an Item 1.05 filing dated June 25, 2026 that ransomware was deployed across portions of its server environment after an unauthorized actor gained network access. Later amendments say certain data was removed from its environment, and the documents do not state how many people are affected or which kinds of personal information were involved.

Entries like this one, in Wednesday’s docket

Wednesdays

Unsubscribe any time.

What happened and when

The filing places the start of the intrusion on or about June 16, 2026. River says it identified the activity on or about June 19, 2026, three days later, and found ransomware deployed across parts of its servers.

The company describes its first response as disabling administrative accounts and pulling systems offline. It engaged an outside forensic firm to examine the incident.

What information was involved

The filings do not list any categories of personal or business information. The original filing treated data access as an open question.

An amendment signed July 10, 2026 reported progress and confirmed that data left the network. The same amendment says the nature of that data was still being worked out. It also stated that the company knew of no fraud tied to the incident.

Operations, finances and later filings

River reported that some operations were affected and that restoration was under way with outside help. It had not decided whether the incident would materially affect its business or finances.

The July 10 amendment also disclosed legal action. The company said it was reviewing them.

The amendment signed July 30, 2026 described an effort to limit further spread of the data.

How did River Financial respond to the ransomware attack?

The filings describe the response in four steps. River disabled the affected administrative accounts and took systems offline. It brought in a third-party forensic firm. It worked with outside cybersecurity professionals to restore operations. And, by its July 30 amendment, it had tried to suppress the stolen data, including by getting the threat actor's word that the data had been deleted. The filings do not say whether a ransom was paid.

What River's later filings say

River's quarterly report for the period ended June 30, 2026, filed on August 4, repeats the account of the intrusion. It says the investigation into the incident's full nature, scope and impact is still going on. It adds that, so far, there is no evidence of customer fraud resulting from the incident, or of any customer account being compromised.

The EDGAR filing index shows no further Item 1.05 amendment after July 30, 2026. River's third-quarter earnings release of October 15, 2026 does not mention the incident.

What the documents leave open

As of the July 30 amendment, the company still had not set out the full picture. It said it would file an amendment within four business days of determining the missing information. The filings mention no notification letters, call-center number, enrollment deadline or count of affected people.

How this disclosure's timing compares

River Financial disclosed 6 days after the discovery date its filing gives. Across the 46 other filings under 8-K Item 1.05 on cisonews.net that date discovery to the day, the median gap is 6 days.

The rule behind an Item 1.05 filing

Form 8-K Item 1.05 is where a public company reports a cybersecurity incident it has determined to be material. Under the rule the SEC adopted on July 26, 2023, the filing is generally due four business days after the company determines that the incident is material. Source: U.S. Securities and Exchange Commission, press release 2023-139. The guide What is SEC Form 8-K Item 1.05, and what counts as a disclosed cyber incident? reads the rule in full, and the glossary defines Form 8-K Item 1.05.

Other financial services incidents on cisonews.net

All financial services incidents

Sources

  1. 2026-06-25 · ARiver Financial Corporation, Form 8-K (SEC EDGAR), published June 25, 2026
  2. 2026-07-06 · ARiver Financial Corporation, Form 8-K/A (SEC EDGAR), published July 6, 2026
  3. 2026-07-10 · ARiver Financial Corporation, Form 8-K/A (SEC EDGAR), published July 10, 2026
  4. 2026-07-17 · ARiver Financial Corporation, Form 8-K/A (SEC EDGAR), published July 17, 2026
  5. 2026-07-30 · ARiver Financial Corporation, Form 8-K/A (SEC EDGAR), published July 30, 2026
  6. 2026-08-04 · ARiver Financial Corporation, Form 10-Q for the quarter ended June 30, 2026 (SEC EDGAR), published August 4, 2026
  7. 2026-10-15 · ARiver Financial Corporation, third-quarter 2026 earnings release, Exhibit 99.1 to Form 8-K (SEC EDGAR), published October 15, 2026
  8. 2026-11-07 · ASEC EDGAR, River Financial Corporation filing index, published November 7, 2026
  9. 2023-07-26 · AU.S. Securities and Exchange Commission, press release 2023-139, published July 26, 2023

Tier A: the organization itself (including notices it filed with a state attorney general), a regulator or SEC EDGAR. Tier B: established press. Each fact on this page carries its supporting passage in the page source.

Entries like this one, in Wednesday’s docket

Wednesdays

Unsubscribe any time.