Skip to content
Welcome, thoughtbot's Giant Robots listeners!Start here
Cybersecurity: Threats and Defences
24JUL

River Financial files fifth breach disclosure

2 min read
18:20UTC

River Financial Corporation told the SEC on 30 July that it still cannot say whether its ransomware intrusion is material or whether personal data was taken, resting partly on the attacker's word that the stolen files were deleted.

TechnologyAssessed
Key takeaway

River's fifth disclosure still rests on an attacker's unverifiable promise that stolen files were deleted.

River Financial Corporation filed an amended Form 8-K with the SEC on 30 July, its fifth disclosure on the same ransomware intrusion, and again reported that it has not determined whether the incident is reasonably likely to have a material effect on its business or financial condition⁠1. Whether personally identifiable information was affected also remains undetermined. An 8-K is the filing a US public company uses to tell investors about events they would want to know before trading; an amendment updates one already made, which is why the count of filings on a single incident can climb.

One sentence in the filing carries more weight than the rest. River obtained representations from the threat actor that it deleted the exfiltrated data⁠2. The company is telling its shareholders, in a document filed with a federal regulator, that part of what it knows about the fate of its stolen files comes from the party that stole them. No independent verification of a deletion claim exists, and none is available: files copied out of a network leave no trace when they are or are not destroyed elsewhere.

The sequence matters as much as the content. River's fourth update on 17 July also left materiality open, which puts two disclosure cycles between the same unanswered question. Each amendment resets the clock in practice without resolving anything, and an investor reading the series learns that the company has counsel, a forensics engagement and no conclusion. The negotiation with the intruder, meanwhile, has produced the only statement anyone has about where the data now sits.

Deep Analysis

In plain English

When a US-listed company suffers a cyberattack that could seriously affect its business, securities rules require it to tell the SEC. River Financial Corporation, the parent of an Alabama bank, disclosed a ransomware attack on 25 June 2026 and has now filed five separate updates on it, most recently on 30 July, without ever answering the two basic questions regulators want answered: was this serious enough to matter financially, and did the attackers steal customers' personal information? Part of the holdup is that River is partly relying on the attackers' own promise that they deleted the stolen data, a promise from criminals that the company has no independent way to check. Until River can verify what was actually taken, it says it can't determine the impact, so each new filing repeats roughly the same unresolved statement six weeks running.

Deep Analysis
Root Causes

River's repeated non-answer traces to a specific evidentiary gap it names itself: the company is relying partly on the threat actor's own representation that exfiltrated data was deleted, a claim from the party with every incentive to say whatever keeps the ransom conversation alive and that River has no independent way to verify.

Item 1.05 filings require a materiality judgement beyond an incident description, and materiality depends on knowing what data left the network. Without independent confirmation of the threat actor's deletion claim, River is structurally stuck: it cannot rule PII exposure in or out, so every subsequent filing can only repeat the same open question in slightly different words.

What could happen next?
  • Risk

    Relying on a threat actor's deletion promise as part of a materiality determination sets a precedent other breached companies may also lean on, despite it being unverifiable.

  • Consequence

    River committed to a further amendment within four business days of determining the necessary information is available, giving the story a concrete next filing to watch for.

First Reported In

Update #12 · KEV deadlines fell from 14 days to three

SEC EDGAR· 3 Aug 2026
Read original →
Different Perspectives
Hospital Sírio-Libanês
Hospital Sírio-Libanês
Hospital Sírio-Libanês said a 21 September attack reached a reporting system for its social projects, possibly exposing patients' and staff identity numbers and health information, while its general patient database was untouched. It notified the ANPD and the Polícia Federal and warned of fraud attempts.
The Foschini Group
The Foschini Group
The Foschini Group told the Johannesburg exchange on 13 October that an attack found on 11 October disrupted IT systems at its TFG London brands, while stores stayed open. It has not identified the attackers or established whether personal data was taken.
FirstVDS
FirstVDS
FirstVDS said attackers used a VMmanager 6 flaw to copy customers' passwords, cloud credentials and cryptocurrency wallets from beneath their virtual servers, and told notified customers to assume theft and rotate credentials. ISPsystem's flaw was not fully fixed on 19 October.
ESET
ESET
ESET says Russia-aligned UAC-0099 phished a Ukrainian grain logistics firm in July 2025 and apparently passed its access to GRU-linked Sandworm, which wiped the company's data that September. It treats the attackers' use of the Yggdrasil network as a first for a state-aligned actor.
JPCERT/CC
JPCERT/CC
JPCERT/CC issued emergency alert AT-2026-0032 on 14 October as EG Secure Solutions confirmed attacks on the SiteGuard Server Edition flaw. It told operators to save diagnostic data before updating, because the update may erase traces of the attack.
Cyber Security Agency of Singapore
Cyber Security Agency of Singapore
The Cyber Security Agency of Singapore said on 20 October that attackers are exploiting Ivanti Connect Secure, seven days after Ivanti's disclosure, having flagged PAN-OS exploitation on 16 October. It issued a PHP2Shell alert on 21 October, the day the fixes shipped.

Written with AI from Lowdown's published reporting. Not individually reviewed by an editor. Editorial standards.