A new ransomware group, identified as n0n, has emerged with an evolved double-extortion tactic that includes threatening to destroy or encrypt victim backups. This strategy aims to eliminate recovery options and increase pressure on victims to pay the ransom. The group, first seen on September 18, 2026, quickly established a leak site and has already claimed over a dozen victims, with a primary focus on the financial services industry in the United States. The initial attack vector appears to be compromised credentials, followed by privilege escalation and data exfiltration before payload deployment. Organizations are advised to prioritize credential hygiene, access monitoring, and the security of their backup infrastructure.
The n0n ransomware group represents a tactical evolution in the ransomware landscape. By explicitly adding the destruction of backups to their threats, they directly counter a primary defense strategy for many organizations. The group's ransom notes make it clear that non-payment will result in the loss of both primary data (through encryption) and recovery data (through destruction). This triple-extortion model (data encryption, data leak, backup destruction) is designed to create a sense of futility and force compliance.
Activity was first observed on September 18, 2026, and by September 22, a Tor-based leak site was active, listing victims. The rapid operational tempo suggests a motivated and potentially experienced group. The primary initial access vector identified in early attacks is the use of stolen credentials, likely purchased from infostealer malware logs available on dark web markets.
Based on initial analysis, n0n's attack chain follows a common but effective pattern:
T1078 - Valid Accounts, specifically with credentials compromised via separate infostealer malware campaigns.T1068 - Exploitation for Privilege Escalation to gain administrative control over the network and key systems, including domain controllers and backup servers.T1046 - Network Service Discovery) to identify critical assets, data repositories, and backup infrastructure.T1562.001 - Disable or Modify Tools) to operate undetected.T1041 - Exfiltration Over C2 Channel) to attacker-controlled infrastructure before encryption begins.T1486 - Data Encrypted for Impact) and targeting backup repositories for destruction or encryption (T1490 - Inhibit System Recovery).The primary targets so far have been in the financial services (23%), technology (15%), retail (15%), and education (15%) sectors. While the initial focus appears to be the United States, the group claims global victims. The business impact of a successful n0n attack is severe. The threat to backups means that traditional incident response playbooks centered on recovery may be ineffective. Victims face the choice of paying a ransom or facing a potentially permanent loss of data, leading to catastrophic operational disruption, significant financial loss, and severe reputational damage. The explicit targeting of backups suggests that recovery time objectives (RTO) could extend from days to weeks or even become indefinite.
No specific file hashes, IP addresses, or domains were mentioned in the source articles.
The following patterns could indicate related activity:
command_line_patternvssadmin.exe delete shadows /all /quietcommand_line_patternwbadmin delete catalog -quietnetwork_traffic_patternlog_sourceSecurity teams should focus on early-stage detection of the TTPs used by n0n.
D3-UGLPA: User Geolocation Logon Pattern Analysis is a key technique here.vssadmin, wbadmin). Use D3-PA: Process Analysis to baseline normal activity and alert on deviations.D3-NTA: Network Traffic Analysis can help identify these anomalies.Enforcing MFA on all external access points and privileged accounts makes it significantly harder for attackers to use stolen credentials.
Mapped D3FEND Techniques:
Strictly control and monitor the use of privileged accounts to limit an attacker's ability to escalate privileges and move laterally.
Maintain immutable, offline, or air-gapped backups to ensure data can be restored even if primary backups are destroyed.
To directly counter n0n's threat of backup destruction, organizations must implement immutable backup storage. This involves configuring backup repositories, whether on-premises or in the cloud, with write-once-read-many (WORM) policies. For cloud storage like AWS S3 or Azure Blob Storage, enable Object Lock or Immutability Policies with a defined retention period. This ensures that once backup data is written, it cannot be altered or deleted, even by an account with administrative privileges, until the retention period expires. This technique effectively neuters the attacker's ability to destroy recovery options, preserving the viability of restoration as a response strategy. It is critical to protect the credentials used to manage these immutability settings with the highest level of security, including MFA and limited access.
Given that n0n's initial access relies on compromised credentials, enforcing Multi-Factor Authentication (MFA) across the entire organization is the single most effective defense. Prioritize deployment on all remote access solutions (VPNs, RDP gateways), cloud services (O365, G-Suite), and especially for all privileged accounts (Domain Admins, local administrators). For maximum security, use phishing-resistant MFA methods like FIDO2 security keys instead of SMS or push-based app authenticators, which are susceptible to MFA fatigue attacks. Implementing MFA raises the barrier for entry, making a simple credential leak insufficient for an attacker to gain a foothold.
The n0n ransomware group's activity is first observed by cybersecurity researchers.
n0n establishes a Tor-hosted leak site and lists over a dozen victims.

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.
CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.