Classification: TLP:CLEAR | Publication Date: 2026-11-11 | Source: ransomware.live leak-site monitoring (single-source for some listings — see Sourcing & Verification) | Nature of data: Unverified threat-actor claims
Executive Summary
Ransomware gang N0N has listed 38 organizations on its dark web leak site, according to monitoring data pulled on 2026-11-11. Fifteen of the most recent listings — Company #197 through Company #211 — were published in a single burst on 2026-11-09, suggesting either a coordinated mass-posting event, batch disclosure following a longer dwell period, or a bluff-and-bulk extortion tactic common among mid-tier ransomware operators.
Targeted countries include the US, NL, IT, CA, and GB. Sector attribution is currently Not Found for all listed organizations, which limits precision in vertical-specific threat modeling but does not diminish the urgency for enterprises in those regions to validate their exposure.
Critically, all 38 listings are single-source — no independent second crawler has confirmed these postings even exist on the gang's infrastructure, let alone that any breach occurred. This briefing treats the data as what it is: unverified threat-actor claims that nonetheless warrant proactive defensive posture adjustments given N0N's known operational tempo.
Sourcing & Verification
- 0 of 38 listings were independently observed by a second leak-site crawler. All 38 listings are single-source, appearing on ransomware.live only without corroboration from an independent monitoring source.
- Inclusion in this briefing reflects the threat actor's claim that these organizations have been compromised. This is not confirmation of a breach. Leak-site postings are accusations by criminal actors, often inflated, fabricated, or recycled from unrelated incidents.
- A named organization may dispute the listing, and a denial is likewise not proof the claim is false — disclosure obligations vary by jurisdiction, and not every incident is reportable. Neither silence nor denial settles the question.
- Security Arsenal will publish corrections as new information becomes available and welcomes contact from any named organization at security@securityarsenal.com.
Threat Actor Profile — N0N
| Attribute | Assessment |
|---|---|
| Known Aliases | N0N (no widely documented aliases at this time) |
| Operational Model | Likely closed-group or small RaaS operation; the burst-posting pattern on 2026-11-09 (15 organizations in one day) is consistent with either a dedicated intrusion team processing a backlog or a small affiliate network reporting up |
| Ransom Demands | Not publicly documented for this campaign; mid-tier groups in this class typically demand between $50K and $2M depending on victim revenue |
| Initial Access Methods | Groups in N0N's operational class commonly exploit exposed VPN appliances, phishing with malicious attachments or links, RDP brute-force / credential stuffing, and supply-chain or managed service provider (MSP) compromise |
| Extortion Model | Double extortion — data exfiltration before encryption, with leak-site publication as leverage. The burst posting of 15 organizations simultaneously is a known pressure tactic to force rapid engagement |
| Average Dwell Time | Unconfirmed for N0N specifically; comparable mid-tier groups average 5–14 days from initial access to detonation, with some extending to 30+ days for data harvesting before triggering encryption |
Operational Notes
The decision to publish 15 listings in a single day, all dated 2026-11-09, is operationally significant. Three plausible explanations:
- Batch processing: N0N accumulated intrusions over weeks and is now processing extortion in bulk, possibly indicating a shift in operational tempo or resource availability.
- Bluff escalation: The group may be posting organizations it has minimal or no actual access to, attempting to exploit fear and reputational pressure. The 0% multi-source corroboration rate makes this hypothesis particularly relevant.
- Access broker liquidation: N0N may have purchased a bundle of accesses from an initial access broker (IAB) and is rushing to monetize before credentials are rotated or detected.
Current Campaign Analysis
Sectors Targeted
Sector data is Not Found for all 38 listings. This is unusual and may indicate one of the following:
- N0N is deliberately withholding sector information to complicate defensive intelligence
- The group lacks mature data processing capabilities and has not yet triaged exfiltrated data
- The listings are speculative or low-confidence claims where the group has not validated what data (if any) it holds
Defensive implication: All sectors in the affected countries should treat this as relevant until sector attribution clarifies.
Geographic Concentration
| Country | Listed Organizations (visible sample) | Notes |
|---|---|---|
| US | 9 of 15 in current window | Primary geographic focus |
| NL | 1 | European expansion consistent with mid-tier group patterns |
| IT | 1 | Southern European presence |
| CA | Listed in aggregate data | Not visible in current 15-org window |
| GB | Listed in aggregate data | Not visible in current 15-org window |
| Unknown (?) | 2 | Country attribution missing for Company #208 and #206 |
The US-centric concentration (60% of the visible window) aligns with the broader ransomware ecosystem's preference for US-based targets due to higher payment propensity and cyber insurance coverage rates.
Victim Profile
Without sector data, revenue and headcount estimates are unreliable. However, the naming convention ("Company #NNN") suggests N0N is using an automated or semi-automated victim intake process, which typically correlates with opportunistic targeting of small-to-midsize enterprises (SMEs) — organizations large enough to pay but often lacking mature security operations.
Posting Frequency & Escalation
- 38 listings in the last 100 postings across the gang's leak site
- 15 listings in a single day (2026-11-09) — a significant burst
- Prior posting cadence is not visible in the current data window, but a 15-in-one-day pattern represents an escalation or anomalous event relative to typical mid-tier group behavior of 2–5 postings per week
CVE Exposure — Hypothesis Only
The following CVEs from the CISA Known Exploited Vulnerabilities catalog are confirmed to be exploited by ransomware operators. There is no evidence linking any of these specific CVEs to any organization listed by N0N. They are presented as sector-level exposure areas that security teams should assess regardless of this specific campaign:
| CVE | Product | KEV Date | Ransomware Relevance |
|---|---|---|---|
| CVE-2026-59310 | Broadcom VMware vCenter | 2026-08-18 | Path traversal — vCenter compromise enables lateral movement across the entire virtualized estate |
| CVE-2026-63077 | JetBrains TeamCity | 2026-08-05 | Deserialization — CI/CD pipeline compromise enables supply-chain payload delivery |
| CVE-2026-20316 | Cisco Secure FMC | 2026-07-29 | Hard-coded password — firewall management plane takeover |
| CVE-2026-50751 | Check Point Security Gateway | 2026-06-08 | Improper authentication in IKEv1 — VPN gateway compromise, direct initial access vector |
| CVE-2026-48027 | Nx Console | 2026-05-27 | Embedded malicious code — developer workstation compromise via supply chain |
Priority: CVE-2026-50751 (Check Point VPN) and CVE-2026-59310 (VMware vCenter) represent the most direct paths to the kind of network-wide access that enables the double-extortion playbook N0N appears to follow. Organizations running these products should verify patch status immediately.
Detection Engineering
Sigma Rules
The following Sigma rules target TTPs associated with N0N's operational class: VPN exploitation, RDP brute force, lateral movement via PsExec/WMI, and pre-encryption data staging.
---
title: N0N Ransomware - Suspicious VPN Authentication Anomaly
id: a1b2c3d4-0001-4e5f-8a9b-n0nvpn000001
status: experimental
description: Detects anomalous VPN authentication patterns consistent with compromised credential use, including impossible travel, off-hours access, and authentication from known VPN/proxy exit nodes. Aligned with N0N's suspected VPN initial access vector.
author: Security Arsenal Threat Intelligence
date: 2026/11/11
references:
- https://securityarsenal.com/darkside
logsource:
category: authentication
product: vpn
detection:
selection_auth_success:
- action: success
- result: success
- outcome: success
filter_business_hours:
timestamp|between: '08:00-18:00'
filter_known_ips:
src_ip|cidr:
- '10.0.0.0/8'
- '172.16.0.0/12'
- '192.168.0.0/16'
condition: selection_auth_success and not filter_business_hours and not filter_known_ips
falsepositives:
- Legitimate remote workers in different time zones
- On-call engineers authenticating off-hours
level: medium
tags:
- attack.initial_access
- attack.t1133
- attack.t1078
---
title: N0N Ransomware - RDP Brute Force Followed by Successful Login
id: a1b2c3d4-0002-4e5f-8a9b-n0nrdp000002
status: experimental
description: Detects multiple failed RDP login attempts (Event ID 4625) from a single source IP followed by a successful login (Event ID 4624) within a 10-minute window. Consistent with RDP brute-force initial access used by mid-tier ransomware groups.
author: Security Arsenal Threat Intelligence
date: 2026/11/11
references:
- https://securityarsenal.com/darkside
logsource:
product: windows
service: security
detection:
selection_failed:
EventID: 4625
LogonType: 10
selection_success:
EventID: 4624
LogonType: 10
condition: selection_failed | count(IpAddress) by IpAddress > 10
timeframe: 10m
falsepositives:
- Legitimate users mistyping passwords repeatedly
- Misconfigured service accounts
level: high
tags:
- attack.credential_access
- attack.t1110
- attack.t1021.001
---
title: N0N Ransomware - Pre-Encryption Data Staging and Exfiltration
id: a1b2c3d4-0003-4e5f-8a9b-n0nexf000003
status: experimental
description: Detects indicators of data staging and exfiltration commonly observed before ransomware detonation, including large archive creation, use of legitimate cloud sync tools in unusual contexts, and high-volume outbound data transfers to non-corporate destinations.
author: Security Arsenal Threat Intelligence
date: 2026/11/11
references:
- https://securityarsenal.com/darkside
logsource:
category: process_creation
product: windows
detection:
selection_archive_tools:
Image|endswith:
- '\7z.exe'
- '\rar.exe'
- '\winrar.exe'
CommandLine|contains:
- ' a '
- '-mx'
- '-hp'
selection_cloud_sync:
Image|endswith:
- '\rclone.exe'
- '\megasync.exe'
- '\rclone.exe'
CommandLine|contains:
- 'copy'
- 'sync'
- 'move'
selection_vss_delete:
Image|endswith:
- '\vssadmin.exe'
- '\wmic.exe'
- '\bcdedit.exe'
CommandLine|contains:
- 'delete shadows'
- 'shadowcopy delete'
- 'recoveryenabled no'
condition: 1 of selection_*
falsepositives:
- Legitimate backup operations using archive tools
- IT administrators managing shadow copies
- Authorized cloud backup solutions
level: high
tags:
- attack.collection
- attack.t1560
- attack.exfiltration
- attack.t1567
- attack.impact
- attack.t1490
KQL — Microsoft Sentinel Hunt Query
// N0N Ransomware - Lateral Movement and Pre-Staging Hunt
// Hunts for PsExec-style service creation, WMI remote execution,
// and suspicious scheduled task creation in the last 7 days.
// Recommended: Run daily across endpoints and servers.
let TimeWindow = 7d;
// PsExec-like remote service creation
let PsExecActivity = SecurityEvent
| where TimeGenerated > ago(TimeWindow)
| where EventID == 7045
| where ServiceName matches regex @"(?i)(psexec|psexesvc|paexec|remcom|csexec)"
| project TimeGenerated, Computer, ServiceName, ServiceFileName, Account, IpAddress
| extend IndicatorType = "PsExec-Style Service Install";
// WMI remote process creation
let WMIActivity = SecurityEvent
| where TimeGenerated > ago(TimeWindow)
| where EventID == 4688
| where ParentProcessName has @"WmiPrvSE.exe"
| where Process !in (@"wmiprvse.exe", @"svchost.exe")
| project TimeGenerated, Computer, Process, CommandLine, Account, ParentProcessName
| extend IndicatorType = "WMI Remote Process Creation";
// Suspicious scheduled task creation (last 7 days)
let SchedTaskActivity = SecurityEvent
| where TimeGenerated > ago(TimeWindow)
| where EventID == 4698
| where TaskName !startswith @"\Microsoft\"
| project TimeGenerated, Computer, TaskName, TaskContent, Account
| extend IndicatorType = "Non-Microsoft Scheduled Task Created";
// Combine all indicators
union PsExecActivity, WMIActivity, SchedTaskActivity
| summarize IndicatorCount = count(), IndicatorTypes = make_set(IndicatorType) by Computer, Account
| where IndicatorCount >= 2
| sort by IndicatorCount desc
PowerShell — Rapid Response Hardening Script
# N0N Ransomware - Rapid Response Hardening & Detection Script
# Run as Administrator on critical servers and endpoints
# Checks: RDP exposure, recent scheduled tasks, VSS status, and suspicious services
Write-Host "=== N0N Rapid Response Check - $(Get-Date -Format 'yyyy-MM-dd HH:mm:ss') ===" -ForegroundColor Cyan
# 1. Check RDP Exposure
Write-Host "`n[1] Checking RDP Exposure..." -ForegroundColor Yellow
$RDPEnabled = (Get-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server').fDenyTSConnections
if ($RDPEnabled -eq 0) {
Write-Host " [!] RDP is ENABLED" -ForegroundColor Red
$RDPPort = (Get-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp').PortNumber
Write-Host " [!] RDP Port: $RDPPort" -ForegroundColor Red
$NLA = (Get-ItemProperty -Path 'HKLM:\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp').UserAuthentication
if ($NLA -ne 1) { Write-Host " [CRITICAL] NLA is DISABLED — RDP is highly exposed" -ForegroundColor Red }
} else {
Write-Host " [+] RDP is disabled" -ForegroundColor Green
}
# 2. Scheduled Tasks Created in Last 7 Days
Write-Host "`n[2] Enumerating Scheduled Tasks (last 7 days)..." -ForegroundColor Yellow
$CutoffDate = (Get-Date).AddDays(-7)
$RecentTasks = Get-ScheduledTask | Where-Object { $_.Date -gt $CutoffDate -and $_.TaskPath -notlike "\Microsoft*" }
if ($RecentTasks) {
$RecentTasks | ForEach-Object {
Write-Host " [!] Task: $($_.TaskName) | Path: $($_.TaskPath) | Created: $($_.Date)" -ForegroundColor Red
}
} else {
Write-Host " [+] No suspicious scheduled tasks found" -ForegroundColor Green
}
# 3. Volume Shadow Copy Status
Write-Host "`n[3] Checking Volume Shadow Copy Status..." -ForegroundColor Yellow
$Shadows = Get-WmiObject Win32_ShadowCopy -ErrorAction SilentlyContinue
if ($Shadows) {
Write-Host " [+] $($Shadows.Count) shadow copies exist" -ForegroundColor Green
} else {
Write-Host " [CRITICAL] No shadow copies found — may have been deleted by threat actor" -ForegroundColor Red
}
$VSSService = Get-Service -Name VSS -ErrorAction SilentlyContinue
if ($VSSService.Status -ne 'Running') {
Write-Host " [!] VSS Service is not running: $($VSSService.Status)" -ForegroundColor Red
}
# 4. Recently Installed Services (last 7 days)
Write-Host "`n[4] Checking for Recently Installed Services..." -ForegroundColor Yellow
$RecentServices = Get-WinEvent -FilterHashtable @{LogName='System'; ID=7045; StartTime=$CutoffDate} -MaxEvents 50 -ErrorAction SilentlyContinue
if ($RecentServices) {
$RecentServices | ForEach-Object {
$svcName = ($_.Message -split "`n")[0] -replace '.*: ',''
Write-Host " [!] Service: $svcName | Time: $($_.TimeCreated)" -ForegroundColor Red
}
} else {
Write-Host " [+] No new services installed in last 7 days" -ForegroundColor Green
}
# 5. Outbound Connections to Suspicious Ports
Write-Host "`n[5] Checking for Suspicious Outbound Connections..." -ForegroundColor Yellow
$SuspiciousPorts = @(4444, 5555, 6666, 8443, 9999, 1337)
$Connections = Get-NetTCPConnection -State Established -ErrorAction SilentlyContinue | Where-Object { $SuspiciousPorts -contains $_.RemotePort -and $_.RemoteAddress -notlike "10.*" -and $_.RemoteAddress -notlike "192.168.*" -and $_.RemoteAddress -notlike "172.16.*" }
if ($Connections) {
$Connections | ForEach-Object {
$ProcName = (Get-Process -Id $_.OwningProcess -ErrorAction SilentlyContinue).ProcessName
Write-Host " [CRITICAL] Connection to $($_.RemoteAddress):$($_.RemotePort) by $ProcName (PID: $($_.OwningProcess))" -ForegroundColor Red
}
} else {
Write-Host " [+] No suspicious outbound connections detected" -ForegroundColor Green
}
Write-Host "`n=== Scan Complete ===" -ForegroundColor Cyan
Incident Response Priorities
T-Minus Detection Checklist — Before Encryption Fires
If you suspect N0N or a similar group is in your environment, look for these indicators before encryption detonates:
| Phase | Indicator | Where to Look |
|---|---|---|
| Initial Access | VPN logins from unusual geographies or ASNs | VPN concentrator logs, firewall logs |
| Credential Access | Kerberoasting (abnormal TGS requests), DCSync attempts | DC Security event logs (Event ID 4769, 4662) |
| Discovery | Mass net group, nltest, arp -a, ipconfig /all execution | EDR process telemetry |
| Lateral Movement | PsExec service creation, WMI remote process, SMB admin share access | Event ID 7045, 4688, network share logs |
| Collection | Large archive creation (7z, RAR), staging in unusual directories | EDR file creation alerts |
| Exfiltration | Rclone, MEGASync, or large outbound transfers to non-corporate cloud | NetFlow, proxy logs, DNS |
| Defense Evasion | VSS deletion, bcdedit modification, security tool tampering | Event ID 4688, EDR tamper alerts |
Critical Assets Prioritized for Exfiltration
Based on the double-extortion playbook used by groups in N0N's class:
- File servers — especially shares containing financial data, HR records, legal documents
- Email databases — executive mailboxes are high-priority for extortion leverage
- Database backups — SQL dumps, Oracle exports, customer PII
- Source code repositories — if present, for IP theft and secondary extortion
- Backup infrastructure — targeted for destruction to eliminate recovery options
Containment Actions — Ordered by Urgency
- IMMEDIATE (0–15 min): Isolate affected segments at the network level; disable compromised accounts; block C2 domains/IPs at the firewall
- URGENT (15–60 min): Reset all domain admin and service account credentials (KRBTGT twice if DCSync suspected); disable RDP externally; force VPN re-authentication for all sessions
- HIGH (1–4 hours): Snapshot critical VMs for forensic preservation; verify backup integrity and isolate backup infrastructure from production; deploy EDR to any unmonitored segments
- MEDIUM (4–24 hours): Full environment sweep with IoCs and hunt queries; review all scheduled tasks, services, and startup items; engage external IR if scope is unclear
Hardening Recommendations
Immediate (24 Hours)
- Patch Check Point Security Gateway (CVE-2026-50751) and VMware vCenter (CVE-2026-59310) — these are confirmed ransomware-exploited vulnerabilities
- Disable external RDP — if RDP must be accessible, place it behind VPN with MFA and restrict to known IP ranges
- Enforce MFA on all VPN access — credential stuffing and brute force are neutralized by MFA
- Verify VSS is running and shadow copies exist —
vssadmin list shadowson all critical servers; alert on deletion - Block PsExec and WMI remote execution where not operationally required — use host firewall rules or application whitelisting
- Review scheduled tasks created in the last 7 days — remove any unauthorized entries
- Enable tamper protection on all EDR/AV agents
Short-Term (2 Weeks)
- Segment the network — isolate backup infrastructure, restrict SMB/RDP between workstation VLANs, implement microsegmentation for critical servers
- Deploy honeypots / canary credentials — low-cost, high-fidelity detection for lateral movement
- Implement application whitelisting on servers — prevent unauthorized binary execution including archive tools used for data staging
- Audit and restrict service accounts — enforce least privilege, implement gMSA where possible, rotate all service account passwords
- Establish offline/immutable backups — at least one copy that is air-gapped or immutable against ransomware encryption
- Review and test IR playbooks — specifically for double-extortion scenarios including data leak response and communication protocols
Related Resources
Security Arsenal Incident Response Managed SOC & MDR Services AlertMonitor Threat Detection From The Dark Side Intel Hub
Is your security operations ready?
Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.