US bank places trust in ransomware crew that promised to delete its data 49%

7/31/2026, 8:41:00 AM

BS Summary: This article contains 22 faulty reasoning types, including Biased Writer Voice, Ambiguity (Equivocation), and Recency Bias, with Negativity Bias as the most egregious example at 56.1% saturation with 185 hits. Analysis detected 926 faulty-reasoning hits from 330 analyzed words, generating a BS Score of 44.5% and a BS Rank of 49% (12,879 of 25,260 articles). This article is better (less manipulative) than 51.00% of the article peer group.

Would you trust a ransomware extortionist to delete the data they stole? 
One bank certainly wants you to. 
Well over a month into a ransomware cleanup job, River Financial Corporation tells regulators that it “took steps to attempt to suppress the affected data, including obtaining representations from the threat actor that it deleted the data in its possession.” 
For context, placing this kind of trust in this kind of individual has been proven to be a bad idea. 
When globo-cops took down LockBit in 2024, they found evidence that victim data was retained even after the victim had paid the extortion demands. 
In its Form 8-K filing with the SEC, River Bank did not explicitly state whether or not it paid any of the criminals’ ransom demands, although ransomware crooks are not commonly known to offer a victim data deletion for free. 
The Register asked the company for a more explicit comment on this matter, but it did not immediately respond. 
River Bank first disclosed its cyber woes to the Securities and Exchange Commission (SEC) on June 16, admitting from the outset that ransomware had been deployed across portions of its servers. 
In response, it took affected systems offline, disabled admin accounts, and brought in external incident responders to determine the full scope of the damage. 
Only July 6, messaging suggested it was aware that some data was “potentially impacted” by the attack, before admitting that certain data was removed from its environment four days later. 
By July 10, River was aware the data had been removed, and two class action lawsuits had been filed against it, to top things off. 
A week later, it told investors that an additional two class actions had been filed, bringing the total to four. 
River has not yet completed its investigation, per its most recent filing, and therefore has not confirmed the full scope or impact of the attack. 
® 
Confirmation Bias
13.9%
Anchoring Bias
9.1%
Availability Heuristic
14.8%
Representativeness Heuristic
7.3%
Hindsight Bias
6.1%
Overconfidence Bias
7.6%
Framing Effect
7.6%
Loss Aversion
0%
Status Quo Bias
0%
Sunk Cost Effect
0%
Optimism Bias
0%
Pessimism Bias
3.6%
Negativity Bias
56.1%
Self-Serving Bias
0%
Fundamental Attribution Error
0%
Actor-Observer Bias
0%
In-Group Bias
0%
Out-Group Homogeneity Bias
0%
Halo Effect
0%
Horn Effect
0%
Dunning-Kruger Effect
0%
Recency Bias
15.2%
Primacy Effect
3.9%
Blind-Spot Bias
0%
Ad Hominem
0%
Straw Man
0%
Appeal to Authority
0%
False Dilemma
3.6%
Slippery Slope
0%
Circular Reasoning
0%
Hasty Generalization
13.3%
Red Herring
0%
Bandwagon
0%
Appeal to Emotion
10%
Begging the Question
0%
Post Hoc (False Cause)
7.6%
Tu Quoque
0%
Burden of Proof
12.1%
Appeal to Nature
0%
Composition/Division
0%
Anecdotal
7.3%
No True Scotsman
0%
Ambiguity (Equivocation)
16.7%
Gambler’s Fallacy
0%
Middle Ground
0%
Personal Incredulity
0%
Special Pleading
5.8%
Genetic Fallacy
0%
Unattributed Quote
12.1%
Quote-first Misdirection
0%
Biased Writer Voice
43.3%
Indoctrination
3.6%
Politically Left Leaning Bias
0%
Politically Right Leaning Bias
0%
Attempt to Sell a Product or Service
0%

330 words analyzed.

Analysis

Hover over highlighted words in the article to view the associated bias or fallacy analysis.