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

River Financial files fifth breach disclosure

2 min read
09:58UTC

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
ENISA
ENISA
ENISA's 22 September threat report found only 23.8 per cent of NoName057(16)'s assessed claims were confirmed by independent availability checks, though the group produced 48 per cent of ideology-driven activity. The agency's numbers show public administration taking 31.8 per cent of attacks, mostly ideological DDoS.
LKA Hamburg
LKA Hamburg
Hamburg's State Criminal Police Office led the operation that took the KillSec leak site on 30 September, with ten countries, Europol and Eurojust. Investigators link the group to around 1,000 suspected attacks, at least 70 in Germany, and the seizure blocks access to at least 110 terabytes of victims' data.
ASOS
ASOS
ASOS said an unauthorised party reached names and contact details on third-party platforms after obtaining an employee's credentials by impersonating a trusted contact. It said it does not believe payment cards or account passwords were affected, and is investigating.
Check Point
Check Point
Check Point updated its advisory on 20 September to say its 9.8-rated VPN certificate flaw had been exploited on Spark firewalls since 12 September, five days after the advisory first appeared, and shipped fixes including R81.20 Take 166. It told customers using only pre-shared-key VPN communities they were not exposed.
Japan's National Police Agency
Japan's National Police Agency
Japan's National Police Agency and National Cybersecurity Office signed advisory AA26-281A and published it on 9 October, naming SoftEther VPN, MicroScan and office-cli and indicators detected since January 2016. Tokyo says the evidence comes from several FBI criminal investigations and that it will deepen cooperation with allies.
CISA
CISA
CISA gave federal agencies three days to fix five flaws from 2015 to 2023 on the day the China advisory named Integrity Technology Group, and set the same clock on 34 of 43 September listings. It treats a named state-linked operation as reason enough to patch old software within the week.