SonicWall’s investigation into the September security breach that exposed customers’ firewall configuration backup files concludes that state-sponsored hackers were behind the attack.
The network security company says that incident responders from Mandiant confirmed that the malicious activity had no impact on SonicWall’s products, firmware, systems, tools, source code, or customer networks.
“The Mandiant investigation is now complete. Their findings confirm that the malicious activity – carried out by a state-sponsored threat actor - was isolated to the unauthorized access of cloud backup files from a specific cloud environment using an …
SonicWall’s investigation into the September security breach that exposed customers’ firewall configuration backup files concludes that state-sponsored hackers were behind the attack.
The network security company says that incident responders from Mandiant confirmed that the malicious activity had no impact on SonicWall’s products, firmware, systems, tools, source code, or customer networks.
“The Mandiant investigation is now complete. Their findings confirm that the malicious activity – carried out by a state-sponsored threat actor - was isolated to the unauthorized access of cloud backup files from a specific cloud environment using an API call,” SonicWall states.
“The incident did not impact SonicWall products or firmware. No other SonicWall systems or tools, source code, or customer networks were disrupted or compromised,” the vendor says.
On September 17, the American company disclosed “an incident that exposed firewall configuration backup files stored in certain MySonicWall accounts.”
An attacker could extract from these files sensitive information, like access credentials and tokens, that could make it “significantly easier” for them to exploit a customer’s firewalls.
The company immediately advised customers to reset their MySonicWall account credentials, temporary access codes, passwords for LDAP, RADIUS, or TACACS+ servers, passwords for L2TP/PPPoE/PPTP WAN interfaces, and shared secrets in IPSec site-to-site and GroupVPN policies.
In an update on October 9, SonicWall stated that the security breach affected all customers who used the company’s cloud backup service to store firewall configuration files.
The investigation is now complete,, and the network security vendor states that the breach was contained to a specific part of its environment and did not impact the safety of its products.
Furthermore, the company assured that the investigated nation-state activity has no connection with attacks from the Akira ransomware gang that targeted MFA-protected SonicWall VPN accounts in late September.
More recently, on October 13, Huntress reported seeing elevated malicious activity targeting SonicWall SSLVPN accounts and successfully compromising over a hundred of them using valid credentials.
Huntress did not find any evidence connecting these attacks to the September firewall configuration files exposure, and SonicWall did not respond to our requests regarding the matter.
[7 Security Best Practices for MCP ](https://www.wiz.io/lp/model-context-protocol-mcp-security-best-practices-cheat-sheet?utm_source=bleepingcomputer&utm_medium=display&utm_campaign=FY26Q3_INB_FORM_MCP-Best Practices-Cheat-Sheet&sfcid=701Py00000TCZuBIAX&utm_term=FY26Q4-bleepingcomputer-article-ad&utm_content=MCP-Best-Practices)
As MCP (Model Context Protocol) becomes the standard for connecting LLMs to tools and data, security teams are moving fast to keep these new services safe.
This free cheat sheet outlines 7 best practices you can start using today.