SonicWall Breach Escalates: 100% of Cloud Backups Confirmed Stolen

SonicWall Confirms 100% of Cloud Backup Customers Had Firewall Configurations Stolen

HIGH
October 6, 2025
5m read
Data BreachSupply Chain AttackCloud Security

Related Entities

Organizations

SonicWall Mandiant

Products & Tech

MySonicWall

Full Report

Executive Summary

In a significant and concerning development, firewall vendor SonicWall has announced a major escalation of its recent security breach. Following an investigation conducted with Mandiant, the company confirmed on October 6, 2025, that an unauthorized party accessed and stole the firewall configuration backup files for 100% of customers using its cloud backup feature via the MySonicWall portal. This revelation is a drastic revision of the company's initial assessment from September 17, 2025, which downplayed the impact to just 5% of its firewall install base. While credentials within the backups are encrypted, the complete exposure of network configurations for all cloud backup users provides a treasure trove of intelligence for threat actors planning future attacks.


Threat Overview

The breach targeted the MySonicWall.com portal, a centralized cloud platform that customers use for product registration, licensing, and, critically, backing up their firewall device configurations. The threat actor successfully compromised this portal and exfiltrated the configuration backup files for every customer who had ever used the service. This represents a serious supply-chain and systemic risk, as the compromise of a single vendor platform has led to the potential exposure of detailed security information for a vast number of downstream customers.

Technical Analysis

The stolen configuration files are a blueprint of a customer's network security posture. Even with encrypted credentials, these files contain a wealth of sensitive information that can be used for attack planning:

  • Network Architecture: Detailed information about internal IP addressing schemes, VLANs, and network segmentation.
  • Firewall Policies (T1595 - Active Scanning): Complete firewall rule sets, revealing which ports are open, what services are exposed, and access control lists (ACLs) between network zones.
  • VPN Configurations: Details of site-to-site and remote access VPN setups, which can be analyzed for weaknesses.
  • Object Definitions: Names and IP addresses of critical internal servers, providing attackers with a map of high-value targets.

While SonicWall states the credentials (e.g., local admin passwords, VPN pre-shared keys) within these files are encrypted, a determined attacker could attempt offline cracking. More importantly, the configuration data itself allows for highly effective and targeted reconnaissance without needing to decrypt the secrets.

Impact Assessment

The impact of this breach is severe and long-lasting for affected SonicWall customers:

  • Pre-Attack Reconnaissance: Threat actors now possess detailed network maps and security policies for thousands of organizations. This allows them to craft highly targeted attacks that bypass specific security controls, making future breaches more likely and harder to detect.
  • Increased Phishing Success: Attackers can use the specific details from configuration files (e.g., server names, usernames) to create extremely convincing spearphishing campaigns.
  • Systemic Risk: The breach highlights the systemic risk of centralized cloud management platforms. A single point of failure at the vendor level can have widespread consequences for the entire customer base.
  • Loss of Confidence: The significant revision from a 5% impact to 100% erodes customer trust in the vendor's ability to manage security incidents and communicate transparently.

Cyber Observables for Detection

Detection efforts must now focus on identifying follow-on attacks that leverage the stolen data.

Type Value Description
network_traffic_pattern Probing/scanning from unknown IPs against ports that are allowed by firewall rules. Attackers may use the stolen configs to identify and target services that are intentionally exposed.
email_address Spearphishing emails containing specific internal hostnames or usernames. Emails that show insider knowledge of the network architecture are highly suspicious.
log_source SonicWall Firewall Logs Monitor for a sudden increase in blocked traffic that appears to be testing the limits of firewall rules, or successful connections from unusual sources.

Detection & Response

  • Assume Compromise: Organizations that have used the SonicWall cloud backup service should operate under the assumption that their network layout and security policies are known to adversaries.
  • Threat Hunting: Proactively hunt for anomalous activity. For example, look for successful authentications to internal services from unexpected IP ranges or unusual lateral movement patterns.
  • Enhanced Monitoring: Increase monitoring on all internet-facing services and critical assets identified in the firewall configuration. Any anomalous access should be treated as a high-priority alert.
  • D3FEND Techniques: Implement D3-UBA: User Behavior Analysis to detect when attackers use stolen knowledge to impersonate legitimate users or access patterns.

Mitigation

SonicWall is urging all affected customers to take immediate action:

  1. Change All Credentials: Immediately change all passwords and pre-shared keys stored in the SonicWall configuration. This includes local administrator passwords, VPN keys, and any other secrets.
  2. Review and Harden Configurations: Treat this as an opportunity for a full security review. Scrutinize all firewall rules, NAT policies, and exposed services. Disable any rules or services that are not absolutely necessary.
  3. Enable Multi-Factor Authentication (MFA): Ensure MFA is enabled on all administrative accounts and remote access VPNs to provide a critical layer of protection against credential abuse.
  4. Limit Management Access: Restrict access to the firewall's management interface to a limited set of trusted IP addresses.

Timeline of Events

1
September 17, 2025
SonicWall initially discloses a breach, claiming only 5% of its firewall install base was affected.
2
October 6, 2025
SonicWall revises its assessment, confirming 100% of cloud backup customers had configuration files stolen.
3
October 6, 2025
This article was published

MITRE ATT&CK Mitigations

Immediately change all passwords and secrets contained within the SonicWall configuration.

Mapped D3FEND Techniques:

Enforce MFA on all administrative and VPN accounts to prevent access even if credentials are cracked.

Mapped D3FEND Techniques:

Audit

M1047enterprise

Increase monitoring and auditing of firewall logs and network traffic for any signs of attack based on the stolen intelligence.

Mapped D3FEND Techniques:

D3FEND Defensive Countermeasures

Given that SonicWall firewall configuration backups containing encrypted credentials were stolen, the immediate priority is to assume all secrets are compromised. Affected organizations must perform a full credential rotation. This involves changing all passwords for local firewall administrator accounts, rotating all VPN pre-shared keys, and updating any other secrets stored in the configuration (e.g., RADIUS secrets, SNMP community strings). This action, a form of authentication cache invalidation, immediately renders the stolen encrypted credentials useless, even if the attackers manage to crack them. This is the most critical first step in responding to the breach.

To build long-term resilience after the credential rotation, organizations must enable multi-factor authentication (MFA) on all SonicWall management interfaces and remote access VPNs. The breach provides attackers with the knowledge of which accounts exist and what services they can access. MFA provides a robust second layer of security that prevents unauthorized access even if an attacker possesses a valid password. This is the most effective control to mitigate the risk of credential-based attacks that are likely to follow this breach. All administrative access should require MFA without exception.

Sources & References

The Week in Breach News: October 15, 2025
Kaseya (kaseya.com) October 6, 2025
October 11, 2025 - Red Dot Security
Red Dot Security (reddotsec.com) October 5, 2025
List of Recent Data Breaches in 2025
Bright Defense (brightdefense.com) October 6, 2025

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Tags

Data BreachSonicWallSupply Chain AttackCloud SecurityFirewall

📢 Share This Article

Help others stay informed about cybersecurity threats

Continue Reading