Fintech firm Marquis filed a lawsuit in the U.S. District Court for the Eastern District of Texas seeking a jury trial, alleging that security failures in SonicWall’s firewall cloud backup service enabled threat actors to later compromise Marquis and deploy ransomware. The complaint claims a 2025 breach at SonicWall exposed sensitive customer firewall configuration backup files, giving attackers detailed insight into how Marquis and other customers configured their perimeter defenses and providing a “blueprint” to bypass them.
Marquis alleges the stolen backup data included emergency administrative access credentials ("scratch codes"), which were used to gain access to Marquis’ internal network, disrupt operations with ransomware, and exfiltrate sensitive data. Marquis stated the incident caused significant operational, reputational, and financial harm, and reported that attackers accessed personally identifiable information tied to customers of some of Marquis’ financial-institution clients, including data elements such as names, dates of birth, postal addresses, and financial information.

Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
9 events from the most recent confirmed update back to the earliest known activity.
After the lawsuit was filed, SonicWall said it was aware of Marquis' claims but had not found technical evidence connecting the MySonicWall incident to the later ransomware attack. The company said it would defend against what it described as unsubstantiated allegations.
On February 23, 2026, Marquis filed suit against SonicWall in the U.S. District Court for the Eastern District of Texas. The complaint alleges gross negligence, misrepresentation, and security failings in SonicWall's cloud backup service that enabled the later ransomware attack on Marquis.
In January 2026, Marquis says it determined its August 2025 intrusion was not caused by an unpatched firewall vulnerability but by attackers leveraging configuration data stolen from SonicWall's cloud backup infrastructure. Reporting also says Mandiant attributed the attack to state-sponsored hackers.
In December 2025, Marquis started notifying affected individuals about the August 2025 network breach. A Texas attorney general listing later indicated at least 400,000 people were affected, with the total expected to rise.
On October 8, 2025, SonicWall updated its assessment and said all customers' firewall backup files had been stolen, not just a small subset. This broader disclosure became central to Marquis' claim that SonicWall misrepresented the incident's scope.
On September 17, 2025, SonicWall publicly disclosed the MySonicWall cloud backup breach and initially said fewer than 5% of customer firewall configuration backup files were exfiltrated. Marquis later claimed this disclosure understated the true scope of the incident.
On August 14, 2025, attackers allegedly used data stolen from SonicWall backups to compromise Marquis' network, bypass MFA, deploy ransomware, and steal sensitive personal and financial information. Marquis says the incident disrupted operations affecting 74 U.S. banks and exposed data tied to customers of its banking and credit-union clients.
SonicWall's MySonicWall cloud backup environment was breached in 2025, resulting in theft of customer firewall configuration backup files. Marquis later alleged the stolen backups included credentials and other data that could be used to bypass protections on downstream customer networks.
Marquis alleges SonicWall made an API code change in February 2025 that created an authentication flaw in the MySonicWall cloud backup service. According to the complaint, attackers could download firewall configuration backups by guessing predictable device serial numbers, and the backups contained sensitive data including MFA scratch codes.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
7 references tracked. Mallory keeps watching after this page renders.
darkreading.com
Open sourceteiss.co.uk
Open sourcethecyberexpress.com
Open sourcebankinfosecurity.com
Open sourcebleepingcomputer.com
Open sourcegovinfosecurity.com
Open sourcetechcrunch.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.