Predatory Sparrow Meteor Malware

SonicWall API Breach: State-Sponsored Attackers Accessed Millions of Firewall Configurations Worldwide

SonicWall has formally confirmed that state-sponsored threat actors were responsible for the September security breach that compromised firewall configuration backup files for all customers using the company's cloud backup service. The conclusion comes after a comprehensive forensic investigation conducted by Google-owned Mandiant, which determined that sophisticated nation-state attackers exploited an API vulnerability to gain unauthorized access to sensitive backup files containing encrypted credentials, access tokens, and firewall configurations.

The Scope of Compromise: Broader Than Initially Disclosed

The September breach represents a significant escalation in targeting of critical infrastructure security providers. SonicWall initially claimed that fewer than 5% of customers were affected and that no files had actually been leaked. However, a subsequent October investigation revealed a dramatically different reality: threat actors accessed firewall configuration backup files for all customers who had utilized the cloud backup service to store preference files.

This evolution from limited impact claims to universal exposure demonstrates the challenges organizations face in rapidly assessing breach scope during active incidents. The configuration files stolen contain encrypted credentials, access tokens, authentication credentials for LDAP/RADIUS/TACACS+ servers, passwords for L2TP/PPPoE/PPTP WAN interfaces, and shared secrets for IPSec site-to-site and GroupVPN policies—the precise sensitive information attackers require to compromise enterprise security infrastructure.

State-Sponsored Attribution: API Exploitation

Mandiant's investigation confirmed that the malicious activity was "isolated to the unauthorized access of cloud backup files from a specific cloud environment using an API call." This technical assessment indicates deliberate, targeted exploitation rather than opportunistic vulnerability discovery. The attackers demonstrated knowledge of SonicWall's cloud infrastructure architecture and API authentication mechanisms, suggesting sophisticated intelligence capabilities typical of nation-state operations.

The API-based attack vector bypassed traditional network perimeter controls and security monitoring, exploiting trust relationships between legitimate API consumers and backend systems. This represents an evolution in nation-state targeting strategies, moving beyond network-layer attacks to exploit application-level interfaces.

What Wasn't Compromised: Important Clarifications

Mandiant's investigation provides critical clarifications about the breach's technical scope. The attack did not compromise:

  • SonicWall products or firmware

  • Source code repositories

  • Other company systems or tools

  • Customer networks directly

  • Products or infrastructure serving other SonicWall services


This contained compromise suggests either that attackers exercised operational discipline, limiting activities to their primary objective, or that SonicWall's broader infrastructure contained adequate security controls preventing lateral movement from the cloud backup environment.

Unrelated Threat Activity: Clearing Confusion

SonicWall explicitly clarified that this breach is unrelated to concurrent attacks against SonicWall SSLVPN devices by the Akira ransomware gang, which successfully compromised MFA-protected VPN accounts in late September. Additionally, October attacks by unidentified threat actors targeting SonicWall SSLVPN accounts using stolen credentials, which compromised over 100 endpoints, show no connection to the September cloud backup incident.

This distinction is important for customers assessing their exposure and determining appropriate remediation strategies. Each attack vector represents separate compromise mechanisms requiring distinct defensive responses.

Customer Remediation Requirements

SonicWall has directed all affected customers to undertake comprehensive credential reset procedures, including:

  • MySonicWall account credentials

  • Temporary access codes

  • LDAP/RADIUS/TACACS+ server passwords

  • L2TP/PPPoE/PPTP WAN interface credentials

  • IPSec and GroupVPN shared secrets

The company released dedicated Online Analysis Tools and Credentials Reset Tools to identify affected services and perform necessary remediation tasks. Customers are directed to MySonicWall.com to verify their device status and implement required changes.

Broader Strategic Implications

The attribution to state-sponsored actors marks an escalation in nation-state targeting of edge security providers. SonicWall explicitly acknowledged this trend in its statement: "As nation-state-backed threat actors increasingly target edge security providers, especially those serving SMB and distributed environments, SonicWall is committed to strengthening its position as a leader."

This targeting strategy reflects geopolitical realities. Compromising firewall configurations provides attackers with unprecedented visibility into network architectures, security policies, and authentication mechanisms across thousands of organizations. SMB and distributed environments represent particularly valuable targets due to typically lower security maturity and resource constraints.

Remediation and Future Posture

SonicWall has implemented security hardening recommendations from Mandiant and engaged external cybersecurity experts to strengthen cloud infrastructure and network security. The company committed to continuous security improvements while acknowledging that state-sponsored operations will continue evolving their tactics.

The incident underscores a critical lesson: organizations must assume that cloud backup services represent attractive attack surfaces requiring equivalent security protections as production systems. The targeting of backup infrastructure-often treated as lower-risk environments—demonstrates that sophisticated attackers recognize backup systems as critical attack pathways to enterprise networks.