February 25, 2026 Source: BleepingComputer 2 min read · 541 words

Marquis sues SonicWall over backup breach that led to ransomware attack

Marquis подає в суд на SonicWall через витік резервної копії, що призвів до атаки ransomware

Timeline: When the Breach Unraveled

The marquis cyber security incident didn't explode overnight. According to BleepingComputer, the breach originated in SonicWall's backup infrastructure—the digital vault where companies store their most critical data. Attackers exploited a vulnerability in this system, gaining unauthorized access. From there, they pivoted to launch ransomware attacks that rippled across the financial sector. Seventy-four U.S. banks felt the impact. Now Marquis Software Solutions is suing SonicWall, arguing the company failed to adequately secure its backup systems.

The lawsuit represents a critical turning point in how the industry views vendor accountability.

The Discovery

How'd they find it? Security researchers detected anomalous activity originating from compromised backup infrastructure. Once the breach was identified, forensic investigators traced the attack chain back to SonicWall's systems. The discovery wasn't a quiet lab finding—it was operational chaos. Banks started seeing encryption notifications. Ransomware demands appeared on screens. Operations ground to a halt.

And then the finger-pointing began.

Marquis discovered their environment had been infiltrated through this backup vector. The company realized they weren't alone. The sonicwall cyber attack map was lighting up across multiple financial institutions simultaneously, all tracing back to the same vulnerability.

Technical Analysis

Here's what actually happened. SonicWall's backup system contained a flaw that allowed unauthenticated attackers to access stored data and credentials. This isn't like a phishing email or social engineering tactic—though those remain common entry points in cyber attacks. This was infrastructure compromise. The backup system held encryption keys, administrative credentials, and system configurations. Everything an attacker needs to move laterally through a network.

The real question is: why wasn't this protected more rigorously?

Backups are supposed to be sacred. They're your insurance policy. When they're compromised, your entire recovery strategy collapses. Attackers grabbed what they needed from backups, then deployed ransomware across victim networks. Is sonicwall a good firewall? That's a separate question—but the backup infrastructure clearly wasn't good enough. The sonicwall cyber security gap here wasn't in perimeter defense. It was in the crown jewels.

Damage Assessment

Seventy-four banks disrupted. That's the headline number. But there's more beneath it.

The financial sector doesn't tolerate downtime gracefully. Customer transactions blocked. ATMs offline. Online banking unavailable. The reputational damage compounds the operational damage. And here's what's particularly nasty: these weren't small regional institutions. These were meaningful players in the U.S. banking system.

Marquis claims SonicWall's negligence directly enabled the attack. The marquis cyber attack was preventable. The marquis cyber security incident represents a catastrophic failure in vendor responsibility. Their lawsuit seeks damages for losses incurred during the incident and the remediation efforts that followed.

Mitigation

SonicWall has released patches addressing the backup vulnerability. Organizations running affected versions need to update immediately. But patching is reactive. The damage is already done for these 74 institutions.

What should happen next? Backup systems need segmentation. Air-gapping critical backups. Multi-factor authentication on backup access. Regular testing of backup integrity and access controls. The basics. The things that should have been in place.

So why does this matter beyond SonicWall and Marquis? Because it exposes a critical weak point in how we protect critical infrastructure. Backups aren't an afterthought. They're not a checkbox on a security audit. They're the difference between a breach and a catastrophe. The sonicwall cyber attack update should remind every organization: audit your backup systems now. If attackers can compromise your backups, your security program has already failed.

Read original article →

// FAQ

How did the SonicWall backup breach lead to the ransomware attack on banks?

Attackers exploited a vulnerability in SonicWall's backup infrastructure to gain access to stored credentials and encryption keys, which they then used to deploy ransomware across victim networks including the 74 affected banks.

Which 74 banks were affected by the SonicWall cyber attack?

BleepingComputer reported that 74 U.S. banks were disrupted by the ransomware attack enabled through the backup breach, though specific bank names weren't disclosed in initial reports.

What is Marquis Software Solutions suing SonicWall for?

Marquis is suing SonicWall for damages resulting from the backup breach that enabled the ransomware attack, claiming the company failed to adequately secure its backup systems and protect customer data.

Concerned about your project's security? Run an automated pentest with AISEC — AI-powered scanner with expert verification. Go to dashboard →