Back to Intelligence

N0N Ransomware Gang: 15 New Victims Claimed on Dark Web — Sector Analysis, Detection Rules & Response Playbook

SA
Security Arsenal Team
October 26, 2026
30 min read

Classification: TLP:CLEAR | Publication Date: 2026-10-26 | Source: ransomware.live leak-site monitoring (single-source for some listings — see Sourcing & Verification) | Nature of data: Unverified threat-actor claims

Executive Summary

Between 2026-10-23 and 2026-10-25, the ransomware group N0N published 15 new victim listings on its dark web leak site, according to monitoring data from ransomware.live. The claimed victims span Energy & Utilities, Technology, Manufacturing, Professional Services, and Healthcare across eight countries — Bulgaria, the United States, Portugal, Argentina, Spain, Ethiopia, Tunisia, and Switzerland.

Six of the fifteen listings were independently observed by a second leak-site crawler, confirming that N0N's infrastructure did publish those claims. The remaining nine appear on a single crawler only. None of these listings confirm that a breach occurred. They represent accusations by a criminal organization, and every named entity should be treated as an alleged — not confirmed — victim.

The pace of 15 postings in three days represents a notable operational tempo for N0N and suggests either a batch-and-dump extortion cycle following a period of sustained intrusion activity, or an aggressive publicity push designed to pressure negotiations. Enterprise security teams in the targeted sectors — particularly those running internet-facing VPN concentrators, VMware vCenter, or Cisco FMC appliances — should treat this as a prompt to validate external attack surface exposure and review detection coverage for N0N's known tradecraft.

Sourcing & Verification

  • 6 of 15 listings were independently observed by a second leak-site crawler. 9 of 15 appear on ransomware.live only, with no second-crawler confirmation that the posting even exists on the gang's site.
  • Inclusion in this briefing reflects the threat actor's claim. It is not confirmation of a breach, intrusion, or data theft at any named organization.
  • A named organization may dispute a listing. A denial is likewise not proof that the claim is false — disclosure obligations vary by jurisdiction, sector, and regulatory framework, and not every security incident triggers a mandatory public report. Neither silence nor denial settles the question. Only the organization itself, its forensic investigators, or its regulator can confirm whether a compromise occurred.
  • Security Arsenal will publish corrections to this briefing as warranted and welcomes contact from any named organization at security@securityarsenal.com.

Threat Actor Profile — N0N

Aliases & Attribution

N0N operates under a minimal public profile with no widely documented aliases in open-source reporting. The group's leak site branding and negotiation portal styling suggest a relatively recent emergence in the ransomware ecosystem, though the operational discipline — consistent posting cadence, multi-sector targeting, and structured victim pages — points to operators with prior experience in established RaaS programs.

Operating Model: RaaS vs. Closed Group

Based on leak site structure and negotiation patterns observed across postings, N0N exhibits characteristics of a closed or semi-closed operation rather than a fully open Ransomware-as-a-Service platform. Key indicators:

  • Consistent leak site formatting across all victim postings, suggesting centralized infrastructure management rather than affiliate-customized portals.
  • No public affiliate recruitment observed on criminal forums.
  • Tight posting cadence — the burst of 15 victims in 72 hours suggests coordinated batch publication rather than independent affiliate-driven uploads.

This does not preclude the use of initial access brokers (IABs) for entry vectors. Like many mid-tier ransomware operations, N0N likely purchases access from brokers who specialize in VPN credential harvesting, RDP brute-forcing, or phishing-delivered backdoors.

Ransom Demands

Specific ransom amounts are not publicly disclosed in the available data. Based on the victim profile — predominantly small-to-midsize businesses (SMBs) across manufacturing, professional services, and regional healthcare — demands are likely calibrated to the low-to-mid six-figure USD range, consistent with industry norms for this victim size class. Larger targets such as energy utilities may face demands approaching seven figures, though this is extrapolation from sector norms, not observed data.

Initial Access Methods

While specific entry vectors for each named victim are not available, N0N's known tradecraft — combined with the CVEs currently listed in CISA KEV with confirmed ransomware exploitation — suggests the following access priorities:

VectorDetail
VPN / Edge Device ExploitationExploitation of internet-facing appliances including Cisco Secure FMC (CVE-2026-20316 — hard-coded password) and Check Point Security Gateway (CVE-2026-50751 — IKEv1 improper authentication). Both are in CISA KEV with confirmed ransomware use.
Phishing with Malicious AttachmentsMacro-enabled documents and embedded links delivering initial-stage loaders. Consistent with broad ransomware ecosystem behavior.
RDP ExposureBrute-force or credential-stuffing attacks against externally exposed Remote Desktop Protocol, particularly in manufacturing and SMB environments with legacy remote access configurations.
Supply Chain / Developer ToolingThe inclusion of CVE-2026-48027 (Nx Console embedded malicious code) and CVE-2026-63077 (JetBrains TeamCity deserialization) in KEV suggests ransomware operators are actively targeting CI/CD pipelines and developer workstations as pivot points.
Virtualization InfrastructureCVE-2026-59310 (VMware vCenter path traversal) provides a direct path to hypervisor-level control — the highest-value target for mass encryption.

Important caveat: These CVEs represent sector-level exposure that ransomware operators — including groups like N0N — are known to exploit. There is no evidence linking any specific CVE to any specific named victim in this briefing. This is hypothesis based on known actor capability and currently exploited vulnerability trends, not forensic attribution.

Double Extortion Approach

N0N follows the standard double extortion model: victims are threatened with both encryption of their environment and public release of exfiltrated data if ransom demands are not met. The leak site serves as the public pressure mechanism. Based on observed behavior:

  • Victim postings include the organization name, sector, and country.
  • Some listings may include sample data or file tree screenshots as proof-of-access, though the current dataset does not include this detail.
  • The batch publication pattern (15 victims in 72 hours) is consistent with a deadline-driven escalation cycle — organizations that did not pay within an initial negotiation window are publicly listed simultaneously to maximize reputational pressure.

Dwell Time

Specific dwell time data for N0N intrusions is not available in this dataset. Industry benchmarks for mid-tier ransomware operations suggest an average dwell time of 5 to 14 days between initial access and ransomware detonation, with data exfiltration typically occurring 48 to 72 hours before encryption. Organizations should assume that by the time a leak site listing appears, the intrusion — if genuine — is already in a post-exfiltration or post-encryption phase.


Current Campaign Analysis

Sector Targeting Breakdown

The 15 claimed victims distribute across the following sectors:

SectorCountPercentage
Manufacturing533%
Professional Services320%
Technology213%
Healthcare213%
Energy & Utilities213%
Other17%
Not Found17%

Manufacturing dominates the victim list at one-third of all postings. This aligns with broader ransomware ecosystem trends — manufacturing organizations frequently run legacy OT/IT converged environments, maintain high operational uptime requirements that create strong extortion leverage, and often lack mature security operations capabilities.

The presence of two healthcare entities (Asisken Asistencia Médica S.A. in Argentina and Arthritis Center of Riverside in the US) and two energy/utilities organizations (TOPLIVO AD in Bulgaria and SunTechnics Fabrisolar AG in Switzerland) is notable. These sectors carry elevated regulatory and public safety implications, increasing extortion pressure.

Geographic Distribution

CountryClaimed Victims
United States5
Bulgaria1
Portugal1
Argentina1
Spain1
Ethiopia1
Tunisia1
Switzerland1

The United States accounts for one-third of claimed victims, consistent with its position as the most-targeted country globally for ransomware operations. However, the spread across eight countries and four continents — including less commonly targeted nations like Ethiopia and Tunisia — suggests either opportunistic access-broker-driven targeting or a deliberate strategy to expand into markets with less mature law enforcement cooperation.

Victim Profile

Based on the named organizations and their sectors, the victim profile skews toward small-to-midsize enterprises:

  • Mach Law APC is a San Diego family law practice — a professional services SMB likely holding sensitive client PII and privileged attorney-client communications.
  • Keidel Supply Company Incorporated is a US-based manufacturing/plumbing supply company — typical mid-market industrial.
  • Andrews Advisory Group LLC is a professional services firm — likely holding financial advisory data.
  • Arthritis Center of Riverside is a specialty medical practice — a small healthcare provider holding protected health information (PHI) subject to HIPAA.
  • TOPLIVO AD is a Bulgarian fuel distribution company — energy sector with potential OT implications.

Estimated annual revenue range across the claimed victim set likely spans $2M to $150M USD, with the majority falling in the $5M–$50M range — the sweet spot for ransomware operations where organizations have enough revenue to pay meaningful ransoms but often lack dedicated security teams.

Posting Frequency & Escalation Patterns

The 15 postings cluster across three consecutive days:

DatePostings
2026-10-256
2026-10-245
2026-10-234

This escalating daily cadence (4 → 5 → 6) suggests a coordinated publication event rather than organic daily discovery. Possible explanations:

  1. Negotiation deadline batch — multiple victims' payment deadlines expired simultaneously, triggering mass publication.
  2. Publicity-driven surge — the gang is building visibility to establish credibility and attract future negotiation compliance.
  3. Access broker inventory dump — a bulk purchase of network access credentials led to a compressed exploitation and extortion timeline.

Regardless of the driver, this tempo indicates active operational capability and should not be dismissed as opportunistic noise.

CVE Correlation (Hypothesis)

The following CVEs are currently listed in CISA KEV with confirmed ransomware exploitation. They represent plausible initial access vectors for campaigns matching N0N's targeting profile. No evidence links any specific CVE to any specific named victim.

CVEProductAttack Surface Relevance
CVE-2026-59310Broadcom VMware vCenterPath traversal — hypervisor-level access enables mass VM encryption. Highest-priority target for ransomware operators.
CVE-2026-63077JetBrains TeamCityDeserialization RCE — CI/CD pipeline compromise enables supply-chain-style lateral movement into production environments.
CVE-2026-20316Cisco Secure FMCHard-coded password — direct administrative access to firewall management plane, enabling network-wide policy manipulation.
CVE-2026-50751Check Point Security GatewayIKEv1 improper authentication — VPN gateway compromise provides authenticated internal network access, bypassing perimeter controls.
CVE-2026-48027Nx ConsoleEmbedded malicious code — developer workstation compromise via poisoned IDE extension, enabling credential theft and source code access.

Organizations running any of these products should verify patch status immediately. The convergence of edge device vulnerabilities (Cisco FMC, Check Point) with virtualization and CI/CD exploitation reflects the current ransomware playbook: enter through the perimeter, escalate through infrastructure, and encrypt at the hypervisor level.


Claimed Victim Listing (2026-10-23 through 2026-10-25)

The following organizations have been listed by N0N on its dark web leak site. Inclusion reflects the threat actor's claim only.

OrganizationSectorCountryPublishedCorroboration
TOPLIVO ADEnergy & UtilitiesBG2026-10-25Multi-Source
Technoleads Services Inc.Technology—2026-10-25Multi-Source
Pure Grow Diamonds Inc.Manufacturing—2026-10-25Multi-Source
Mach Law APCProfessional ServicesUS2026-10-25Multi-Source
Keidel Supply Company IncorporatedManufacturingUS2026-10-25Multi-Source
Andrews Advisory Group LLCProfessional ServicesUS2026-10-25Multi-Source
Texcar Inc.Manufacturing—2026-10-24Single-Source
GPIC Projectos Con Instalacoes LdaManufacturingPT2026-10-24Single-Source
Asisken Asistencia Médica S.A.HealthcareAR2026-10-24Single-Source
Adirondack Networks, Inc.TechnologyUS2026-10-24Single-Source
Arthritis Center of RiversideHealthcareUS2026-10-24Single-Source
Company #110Not FoundES2026-10-23Single-Source
Horn of Africa Regional Environment Centre and NetworkOtherET2026-10-23Single-Source
PROTEX ConfectionManufacturingTN2026-10-23Single-Source
SunTechnics Fabrisolar AGEnergy & UtilitiesCH2026-10-23Single-Source

Detection Engineering

The following detection content targets TTPs consistent with N0N's known operational playbook: VPN exploitation for initial access, PsExec/WMI-based lateral movement, data staging with common archiving tools, and pre-encryption shadow copy deletion. These rules are mapped to MITRE ATT&CK and designed for deployment in Sigma-compatible SIEM pipelines and Microsoft Sentinel.

YAML
---
title: N0N Ransomware - PsExec Service Installation for Lateral Movement
id: a1b2c3d4-e5f6-7890-abcd-ef1234567890
status: production
description: Detects PsExec-style service creation events associated with N0N ransomware lateral movement. Monitors for service installation events with PsExec default naming conventions, ADMIN$ share writes, and remote service execution patterns observed in N0N campaigns.
author: Security Arsenal Threat Intelligence
references:
  - https://attack.mitre.org/techniques/T1021/002/
  - https://attack.mitre.org/techniques/T1569/002/
date: 2026/10/26
tags:
  - attack.lateral_movement
  - attack.t1021.002
  - attack.t1569.002
  - attack.execution
logsource:
  category: service_creation
  product: windows
  service: system
detection:
  selection_psexec_name:
    ServiceName|contains:
      - 'PSEXESVC'
      - 'PsExec'
  selection_psexec_binary:
    ImagePath|contains:
      - '\\ADMIN$\\'
      - '\\IPC$\\'
      - '\PSEXESVC.exe'
  selection_suspicious_svc:
    ImagePath|contains:
      - 'cmd.exe /c'
      - 'powershell.exe -enc'
      - 'powershell.exe -e '
      - '\\Users\\Public\\'
      - '\\Windows\\Temp\\'
      - '\\ProgramData\\'
  selection_suspicious_svc_name:
    ServiceName|contains:
      - 'update'
      - 'svc'
      - 'win'
      - 'sys'
  condition: selection_psexec_name or selection_psexec_binary or (selection_suspicious_svc and selection_suspicious_svc_name)
falsepositives:
  - Legitimate administrative use of PsExec by IT teams
  - SCCM or other management tools that install remote services
  - Vulnerability scanners using PsExec-style deployment
level: high
---
title: N0N Ransomware - Volume Shadow Copy Deletion via Multiple Methods
id: b2c3d4e5-f6a7-8901-bcde-f12345678901
status: production
description: Detects deletion or manipulation of Volume Shadow Copies using vssadmin, wmic, diskshadow, or PowerShell — a hallmark pre-encryption action by N0N and virtually all ransomware operations to inhibit recovery. Correlates multiple deletion methods and flags execution within suspicious parent process contexts.
author: Security Arsenal Threat Intelligence
references:
  - https://attack.mitre.org/techniques/T1490/
  - https://attack.mitre.org/techniques/T1059/001/
date: 2026/10/26
tags:
  - attack.impact
  - attack.t1490
  - attack.defense_evasion
logsource:
  category: process_creation
  product: windows
detection:
  selection_vssadmin:
    Image|endswith: '\vssadmin.exe'
    CommandLine|contains:
      - 'delete shadows'
      - 'Delete Shadows'
      - 'resize shadowstorage'
  selection_wmic:
    Image|endswith: '\wmic.exe'
    CommandLine|contains:
      - 'shadowcopy'
      - 'ShadowCopy'
  selection_diskshadow:
    Image|endswith: '\diskshadow.exe'
    CommandLine|contains:
      - 'delete shadows'
      - 'Delete Shadows'
  selection_powershell_vss:
    Image|endswith:
      - '\powershell.exe'
      - '\pwsh.exe'
    CommandLine|contains:
      - 'Get-WmiObject Win32_Shadowcopy'
      - 'Get-CimInstance Win32_ShadowCopy'
      - 'Remove-WmiObject'
      - 'Remove-CimInstance'
      - 'Delete()'
  selection_bcdedit:
    Image|endswith: '\bcdedit.exe'
    CommandLine|contains:
      - 'recoveryenabled'
      - 'bootstatuspolicy'
      - 'ignoreallfailures'
  filter_known_admin:
    ParentImage|endswith:
      - '\Veeam.Backup.Service.exe'
      - '\BackupExec.exe'
      - '\wbadmin.exe'
  condition: 1 of selection_* and not filter_known_admin
falsepositives:
  - Backup software performing shadow copy lifecycle management
  - IT administrators manually clearing shadow copies for disk space
  - System maintenance scripts using bcdedit for boot configuration
level: critical
---
title: N0N Ransomware - Data Staging and Exfiltration via Archive Tools and Cloud Sync
id: c3d4e5f6-a7b8-9012-cdef-123456789012
status: production
description: Detects data staging behavior consistent with N0N ransomware pre-exfiltration activity. Identifies bulk file archiving with 7-Zip, WinRAR, or tar in non-standard directories, execution of cloud sync tools (rclone, MEGAcmd) from unusual paths, and high-volume file copy operations to staging directories before encryption.
author: Security Arsenal Threat Intelligence
references:
  - https://attack.mitre.org/techniques/T1560/001/
  - https://attack.mitre.org/techniques/T1567/002/
  - https://attack.mitre.org/techniques/T1074/001/
date: 2026/10/26
tags:
  - attack.collection
  - attack.t1560.001
  - attack.t1074.001
  - attack.exfiltration
  - attack.t1567.002
logsource:
  category: process_creation
  product: windows
detection:
  selection_archive_tools:
    Image|endswith:
      - '\7z.exe'
      - '\7za.exe'
      - '\7zg.exe'
      - '\rar.exe'
      - '\winrar.exe'
  selection_archive_args:
    CommandLine|contains:
      - ' a '
      - ' -r'
      - ' -mx'
      - ' -p'
      - '*.7z'
      - '*.rar'
      - '*.zip'
  selection_staging_dirs:
    CommandLine|contains:
      - '\\Users\\Public\\'
      - '\\Windows\\Temp\\'
      - '\\ProgramData\\'
      - 'C:\\Temp\\'
      - 'C:\\staging'
      - 'C:\\backup'
      - 'C:\\exfil'
  selection_cloud_sync:
    Image|endswith:
      - '\rclone.exe'
      - '\megacmd.exe'
      - '\MEGAcmd.exe'
      - '\rclone-v*.exe'
  selection_cloud_args:
    CommandLine|contains:
      - 'copy'
      - 'sync'
      - 'move'
      - '--config'
      - 'mega.nz'
      - 'drive.google.com'
      - 'dropbox.com'
  condition: (selection_archive_tools and selection_archive_args and selection_staging_dirs) or (selection_cloud_sync and selection_cloud_args)
falsepositives:
  - Legitimate backup operations using 7-Zip or WinRAR
  - IT administrators staging files for deployment
  - Legitimate use of rclone for cloud backup by power users
level: high

KQL Hunt Query — Microsoft Sentinel

The following query hunts for pre-ransomware staging and lateral movement indicators associated with N0N's known toolset. It chains multiple weak signals — suspicious service creation, shadow copy tampering, archive tool execution, and outbound data volume anomalies — into a composite hunt designed for a 7-day lookback.

KQL — Microsoft Sentinel / Defender
// N0N Ransomware - Pre-Encryption Staging & Lateral Movement Composite Hunt
// Lookback: 7 days | Author: Security Arsenal TI | 2026-10-26
// MITRE: T1021.002, T1490, T1560.001, T1567.002, T1074.001

let Lookback = 7d;

// Signal 1: Suspicious service installations (PsExec-style)
let SuspiciousServices =
    SecurityEvent
    | where TimeGenerated >= ago(Lookback)
    | where EventID == 7045
    | where ServiceName has_any ("PSEXESVC", "PsExec", "update", "svc", "winsvc", "syssvc")
       or ServiceFileName has_any ("ADMIN$", "IPC$", "PSEXESVC", "\\Users\\Public\\", "\\Windows\\Temp\\", "\\ProgramData\\")
    | project ServiceAlert_Time=TimeGenerated, Computer, ServiceName, ServiceFileName, ServiceAccount=Account, ServiceAlert_SourceIP=IpAddress
    | extend SignalType = "SuspiciousServiceInstall";

// Signal 2: Shadow copy deletion attempts
let ShadowCopyDeletion =
    SecurityEvent
    | where TimeGenerated >= ago(Lookback)
    | where EventID == 4688
    | where (Process has "vssadmin" and CommandLine has "delete shadows")
       or (Process has "wmic" and CommandLine has "shadowcopy")
       or (Process has "diskshadow" and CommandLine has "delete")
       or (Process has "bcdedit" and CommandLine has_any ("recoveryenabled", "ignoreallfailures"))
    | project ShadowAlert_Time=TimeGenerated, Computer, ShadowCmd=CommandLine, ShadowParent=ParentProcessName, ShadowAccount=Account
    | extend SignalType = "ShadowCopyDeletion";

// Signal 3: Archive/staging tool execution from suspicious paths
let StagingActivity =
    SecurityEvent
    | where TimeGenerated >= ago(Lookback)
    | where EventID == 4688
    | where (Process has_any ("7z.exe", "7za.exe", "rar.exe", "winrar.exe")
            and CommandLine has_any ("\\Users\\Public\\", "\\Windows\\Temp\\", "\\ProgramData\\", "C:\\Temp"))
       or (Process has_any ("rclone.exe", "megacmd.exe"))
    | project StagingAlert_Time=TimeGenerated, Computer, StagingProcess=Process, StagingCmd=CommandLine, StagingAccount=Account
    | extend SignalType = "DataStaging";

// Signal 4: High outbound data transfer (potential exfiltration)
let HighOutbound =
    AzureNetworkAnalytics_CL
    | where TimeGenerated >= ago(Lookback)
    | where FlowDirection_s == "O"  // Outbound flows
    | summarize TotalBytesOut=sum(tolong(BytesSent_s)), FlowCount=count()
        by SrcIP_s, DestIP_s, DestPort_d
    | where TotalBytesOut > 1073741824  // > 1 GB outbound to a single destination
    | extend SignalType = "HighOutboundTransfer"
    | project OutboundAlert_Time=TimeGenerated, SrcIP_s, DestIP_s, DestPort_d, TotalBytesOut, FlowCount, SignalType;

// Correlate: machines with 2+ distinct signals within 24 hours
let CorrelatedMachines =
    union
        (SuspiciousServices | project Computer, SignalType, AlertTime=ServiceAlert_Time),
        (ShadowCopyDeletion | project Computer, SignalType, AlertTime=ShadowAlert_Time),
        (StagingActivity | project Computer, SignalType, AlertTime=StagingAlert_Time)
    | summarize DistinctSignals=dcount(SignalType), SignalTypes=make_set(SignalType), FirstSeen=min(AlertTime), LastSeen=max(AlertTime)
        by Computer
    | where DistinctSignals >= 2
    | extend RiskScore = case(
        DistinctSignals >= 3, "CRITICAL — Multi-signal ransomware staging detected",
        DistinctSignals == 2 and SignalTypes has "ShadowCopyDeletion", "HIGH — Shadow copy tampering with additional staging signal",
        "MEDIUM — Multiple suspicious signals detected"
    )
    | sort by DistinctSignals desc, FirstSeen asc;

CorrelatedMachines

PowerShell Rapid Response Script

Deploy this script on endpoints or servers suspected of N0N pre-encryption activity. It performs a rapid triage: checks for recently created scheduled tasks, audits Volume Shadow Copy integrity, identifies recently created services, and flags RDP exposure.

PowerShell
#Requires -RunAsAdministrator
<#
.SYNOPSIS
    N0N Ransomware Rapid Triage Script
    Security Arsenal Threat Intelligence | 2026-10-26
.DESCRIPTION
    Performs rapid endpoint triage for indicators consistent with N0N ransomware
    pre-encryption staging. Checks: scheduled tasks, VSS integrity, new services,
    RDP exposure, suspicious processes, and recent archive tool artifacts.
.NOTES
    Run as Administrator. Output is written to console and a local report file.
    This script is READ-ONLY. It makes no system modifications.
#>

$ReportPath = "$env:TEMP\N0N_Triage_$(Get-Date -Format 'yyyyMMdd_HHmmss').txt"
$LookbackDays = 7
$LookbackDate = (Get-Date).AddDays(-$LookbackDays)
$Findings = @()

function Write-Finding {
    param([string]$Severity, [string]$Category, [string]$Detail)
    $entry = "[$Severity] [$Category] $Detail"
    $script:Findings += $entry
    Write-Host $entry -ForegroundColor $(switch($Severity){"CRITICAL"{"Red"}"HIGH"{"DarkYellow"}"MEDIUM"{"Yellow"}default{"Cyan"}})
}

Write-Host "============================================" -ForegroundColor Cyan
Write-Host " N0N Ransomware Rapid Triage — $(Get-Date)" -ForegroundColor Cyan
Write-Host " Hostname: $env:COMPUTERNAME" -ForegroundColor Cyan
Write-Host "============================================" -ForegroundColor Cyan

# === CHECK 1: Recently Created Scheduled Tasks (Persistence) ===
Write-Host "`n[CHECK 1] Scheduled Tasks Created in Last $LookbackDays Days" -ForegroundColor White
try {
    $recentTasks = Get-ScheduledTask | Where-Object { $_.Date -ge $LookbackDate -and $_.TaskPath -notlike "\Microsoft\*" }
    if ($recentTasks) {
        foreach ($task in $recentTasks) {
            $taskActions = ($task.Actions | ForEach-Object { "$($_.Execute) $($_.Arguments)" }) -join "; "
            Write-Finding "HIGH" "Persistence" "Task: $($task.TaskName) | Path: $($task.TaskPath) | Action: $taskActions | Created: $($task.Date)"
        }
    } else {
        Write-Host "  [OK] No non-Microsoft scheduled tasks created in the last $LookbackDays days." -ForegroundColor Green
    }
} catch {
    Write-Host "  [ERROR] Could not enumerate scheduled tasks: $_" -ForegroundColor Red
}

# === CHECK 2: Volume Shadow Copy Status ===
Write-Host "`n[CHECK 2] Volume Shadow Copy Integrity" -ForegroundColor White
try {
    $shadows = Get-WmiObject Win32_ShadowCopy -ErrorAction SilentlyContinue
    if ($shadows) {
        Write-Host "  [OK] $($shadows.Count) shadow copies exist." -ForegroundColor Green
        foreach ($shadow in $shadows) {
            Write-Host "    - ID: $($shadow.ID) | Volume: $($shadow.VolumeName) | Created: $($shadow.InstallDate)" -ForegroundColor Green
        }
    } else {
        Write-Finding "CRITICAL" "Anti-Recovery" "No Volume Shadow Copies found. This may indicate pre-encryption cleanup by ransomware operators."
    }

    # Check VSS service state
    $vssService = Get-Service -Name VSS -ErrorAction SilentlyContinue
    if ($vssService -and $vssService.Status -ne "Running") {
        Write-Finding "HIGH" "Anti-Recovery" "VSS service is $($vssService.Status) (expected: Running or Manual-triggered). Service may have been disabled."
    }

    # Check boot recovery settings (bcdedit)
    $bcdOutput = bcdedit 2>&1 | Out-String
    if ($bcdOutput -match "recoveryenabled\s+No") {
        Write-Finding "CRITICAL" "Anti-Recovery" "Boot recovery is DISABLED via bcdedit. Ransomware frequently disables recovery to prevent rollback."
    }
    if ($bcdOutput -match "ignoreallfailures\s+Yes") {
        Write-Finding "CRITICAL" "Anti-Recovery" "Boot status policy set to ignoreallfailures. This is a common ransomware anti-recovery technique."
    }
} catch {
    Write-Host "  [ERROR] Could not check shadow copies: $_" -ForegroundColor Red
}

# === CHECK 3: Recently Created Services ===
Write-Host "`n[CHECK 3] Services Created in Last $LookbackDays Days" -ForegroundColor White
try {
    $recentServices = Get-CimInstance Win32_Service | Where-Object {
        $_.InstallDate -and ([Management.ManagementDateTimeConverter]::ToDateTime($_.InstallDate)) -ge $LookbackDate
    }
    # Fallback: check via event log
    if (-not $recentServices) {
        $serviceEvents = Get-WinEvent -FilterHashtable @{LogName='System'; Id=7045; StartTime=$LookbackDate} -MaxEvents 50 -ErrorAction SilentlyContinue
        if ($serviceEvents) {
            foreach ($evt in $serviceEvents) {
                $xml = [xml]$evt.ToXml()
                $svcName = ($xml.Event.EventData.Data | Where-Object {$_.Name -eq 'ServiceName'}).'#text'
                $svcPath = ($xml.Event.EventData.Data | Where-Object {$_.Name -eq 'ImagePath'}).'#text'
                Write-Finding "HIGH" "LateralMovement" "New service: $svcName | Binary: $svcPath | Time: $($evt.TimeCreated)"
            }
        } else {
            Write-Host "  [OK] No new services detected in the last $LookbackDays days." -ForegroundColor Green
        }
    } else {
        foreach ($svc in $recentServices) {
            Write-Finding "HIGH" "LateralMovement" "Service: $($svc.Name) | Path: $($svc.PathName) | State: $($svc.State)"
        }
    }
} catch {
    Write-Host "  [ERROR] Could not enumerate services: $_" -ForegroundColor Red
}

# === CHECK 4: RDP Exposure Assessment ===
Write-Host "`n[CHECK 4] RDP Exposure" -ForegroundColor White
try {
    $rdpEnabled = (Get-ItemProperty "HKLM:\System\CurrentControlSet\Control\Terminal Server" -Name fDenyTSConnections -ErrorAction SilentlyContinue).fDenyTSConnections
    if ($rdpEnabled -eq 0) {
        Write-Finding "MEDIUM" "InitialAccess" "RDP is ENABLED on this host."
        $rdpPort = (Get-ItemProperty "HKLM:\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp" -Name PortNumber -ErrorAction SilentlyContinue).PortNumber
        Write-Host "    RDP Port: $rdpPort" -ForegroundColor Yellow
        if ($rdpPort -eq 3389) {
            Write-Finding "HIGH" "InitialAccess" "RDP is running on the DEFAULT port (3389). This is a primary target for brute-force attacks."
        }

        # Check NLA
        $nlaEnabled = (Get-ItemProperty "HKLM:\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp" -Name UserAuthentication -ErrorAction SilentlyContinue).UserAuthentication
        if ($nlaEnabled -ne 1) {
            Write-Finding "HIGH" "InitialAccess" "Network Level Authentication (NLA) is DISABLED. RDP is exposed to pre-authentication attacks."
        }

        # Check for external RDP in firewall rules
        $rdpFirewall = Get-NetFirewallRule -DisplayGroup "Remote Desktop" -ErrorAction SilentlyContinue | Where-Object { $_.Enabled -eq "True" -and $_.Direction -eq "Inbound" }
        if ($rdpFirewall) {
            Write-Finding "MEDIUM" "InitialAccess" "$($rdpFirewall.Count) inbound RDP firewall rules are ENABLED. Verify RDP is not exposed to the internet."
        }
    } else {
        Write-Host "  [OK] RDP is disabled on this host." -ForegroundColor Green
    }
} catch {
    Write-Host "  [ERROR] Could not assess RDP configuration: $_" -ForegroundColor Red
}

# === CHECK 5: Suspicious Running Processes ===
Write-Host "`n[CHECK 5] Suspicious Running Processes" -ForegroundColor White
$suspiciousProcesses = @("vssadmin", "wmic", "diskshadow", "7z", "7za", "rar", "winrar", "rclone", "megacmd", "psexec", "psexesvc", "cobaltstrike", "beacon", "mimikatz", "procdump", "comsvcs")
try {
    $running = Get-Process | Where-Object { $proc = $_.ProcessName.ToLower(); $suspiciousProcesses | Where-Object { $proc -like "*$_*" } }
    if ($running) {
        foreach ($proc in $running) {
            Write-Finding "CRITICAL" "ActiveThreat" "Suspicious process running: $($proc.ProcessName) (PID: $($proc.Id)) | Path: $($proc.Path)"
        }
    } else {
        Write-Host "  [OK] No known ransomware-associated tools found in running processes." -ForegroundColor Green
    }
} catch {
    Write-Host "  [ERROR] Could not enumerate processes: $_" -ForegroundColor Red
}

# === CHECK 6: Recent Archive Files in Staging Directories ===
Write-Host "`n[CHECK 6] Archive Files in Common Staging Locations" -ForegroundColor White
$stagingDirs = @("C:\Users\Public", "C:\Windows\Temp", "C:\ProgramData", "C:\Temp", "C:\staging", "C:\exfil")
foreach ($dir in $stagingDirs) {
    if (Test-Path $dir) {
        $archives = Get-ChildItem -Path $dir -Recurse -Include "*.7z","*.rar","*.zip","*.tar","*.gz" -ErrorAction SilentlyContinue |
            Where-Object { $_.LastWriteTime -ge $LookbackDate -and $_.Length -gt 10MB }
        if ($archives) {
            foreach ($file in $archives) {
                Write-Finding "HIGH" "DataStaging" "Archive found: $($file.FullName) | Size: $([math]::Round($file.Length/1MB,2)) MB | Modified: $($file.LastWriteTime)"
            }
        }
    }
}
if (-not ($Findings | Where-Object { $_ -match "DataStaging" })) {
    Write-Host "  [OK] No large recently-modified archives found in staging directories." -ForegroundColor Green
}

# === CHECK 7: Recent Failed Logons (Brute Force Indicator) ===
Write-Host "`n[CHECK 7] Failed Logon Events (Last 24 Hours)" -ForegroundColor White
try {
    $failedLogons = Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4625; StartTime=(Get-Date).AddDays(-1)} -MaxEvents 100 -ErrorAction SilentlyContinue
    if ($failedLogons) {
        $groupedFailures = $failedLogons | Group-Object { $_.Properties[19].Value } | Sort-Object Count -Descending
        foreach ($group in $groupedFailures) {
            if ($group.Count -gt 10) {
                Write-Finding "HIGH" "InitialAccess" "Account '$($group.Name)': $($group.Count) failed logon attempts in 24h — possible brute force."
            }
        }
        if ($failedLogons.Count -gt 50) {
            Write-Finding "HIGH" "InitialAccess" "Total: $($failedLogons.Count) failed logon events in 24h. Elevated failure volume detected."
        }
    } else {
        Write-Host "  [OK] No significant failed logon volume detected." -ForegroundColor Green
    }
} catch {
    Write-Host "  [ERROR] Could not query security log: $_" -ForegroundColor Red
}

# === SUMMARY ===
Write-Host "`n============================================" -ForegroundColor Cyan
Write-Host " TRIAGE SUMMARY" -ForegroundColor Cyan
Write-Host "============================================" -ForegroundColor Cyan
$criticalCount = ($Findings | Where-Object { $_ -match "\[CRITICAL\]" }).Count
$highCount = ($Findings | Where-Object { $_ -match "\[HIGH\]" }).Count
$mediumCount = ($Findings | Where-Object { $_ -match "\[MEDIUM\]" }).Count
Write-Host "  CRITICAL findings: $criticalCount" -ForegroundColor $(if($criticalCount -gt 0){"Red"}else{"Green"})
Write-Host "  HIGH findings:     $highCount" -ForegroundColor $(if($highCount -gt 0){"DarkYellow"}else{"Green"})
Write-Host "  MEDIUM findings:   $mediumCount" -ForegroundColor $(if($mediumCount -gt 0){"Yellow"}else{"Green"})
Write-Host ""
if ($criticalCount -gt 0) {
    Write-Host "  *** IMMEDIATE ACTION REQUIRED — Critical indicators of ransomware staging detected. ***" -ForegroundColor Red
    Write-Host "  *** Isolate this host from the network and initiate incident response procedures. ***" -ForegroundColor Red
} elseif ($highCount -gt 0) {
    Write-Host "  ** ELEVATED RISK — Investigate HIGH findings immediately. Consider enhanced monitoring. **" -ForegroundColor DarkYellow
} else {
    Write-Host "  No critical or high-severity findings. Continue standard monitoring." -ForegroundColor Green
}

# Write report to file
$Findings | Out-File -FilePath $ReportPath -Encoding UTF8
Write-Host "`nReport saved to: $ReportPath" -ForegroundColor Cyan

Incident Response Priorities

T-Minus Detection Checklist — Before Encryption Fires

Ransomware operations follow a predictable kill chain. The window between initial access and detonation — typically 5 to 14 days — represents the detection opportunity. The following checklist is ordered by expected sequence in N0N's operational timeline:

PhaseTime Before EncryptionDetection Indicators
Initial AccessDays 1-3VPN/firewall authentication anomalies, new account creation, impossible travel logins, exploit attempts against CVE-2026-20316, CVE-2026-50751
Persistence & DiscoveryDays 2-5New scheduled tasks, suspicious service installations, net group "Domain Admins" /domain enumeration, nltest / dsquery reconnaissance
Credential AccessDays 3-7LSASS memory access by non-system processes, procdump or comsvcs.dll execution, DCSync-style replication requests, Mimikatz artifacts in memory
Lateral MovementDays 4-10PsExec service creation (Event 7045), WMI process execution on remote hosts (Event 4688 with parent WmiPrvSE.exe), RDP sessions from unexpected source hosts, Cobalt Strike beacon C2 traffic
Data StagingDays 5-12Large archive files (.7z, .rar) in \\Users\\Public\\ or \\ProgramData\\, rclone/MEGAcmd execution, anomalous outbound data volume (>1 GB to single external destination)
Anti-RecoveryHours before encryptionvssadmin delete shadows, bcdedit recovery modification, backup service termination, backup catalog deletion
EncryptionDetonationMass file rename/extension change, ransom note creation in multiple directories, wevtutil cl log clearing

Key principle: If you detect signals from the Data Staging or Anti-Recovery phases, you are likely hours to minutes from encryption. Immediate containment is required.

Critical Assets N0N Historically Prioritizes for Exfiltration

Based on sector targeting patterns and standard double-extortion methodology, organizations should assume the following data categories are primary exfiltration targets:

SectorHigh-Value Exfiltration Targets
Healthcare (Arthritis Center of Riverside, Asisken Asistencia Médica)Patient records (PHI/PII), insurance billing data, prescription records, clinical notes
Professional Services / Legal (Mach Law APC, Andrews Advisory Group)Client files, privileged attorney-client communications, financial advisory data, tax records
Energy & Utilities (TOPLIVO AD, SunTechnics Fabrisolar AG)SCADA/OT network diagrams, engineering specifications, customer billing data, regulatory compliance documentation
Manufacturing (Keidel Supply, Texcar, GPIC, PROTEX Confection, Pure Grow Diamonds)CAD/engineering drawings, supply chain data, customer contracts, proprietary process documentation, ERP databases
Technology (Technoleads Services, Adirondack Networks)Source code, API credentials, customer databases, network architecture diagrams, MSP client access credentials

Containment Actions — Ordered by Urgency

If ransomware staging indicators are confirmed in your environment, execute these actions in order:

  1. Isolate affected hosts immediately — VLAN quarantine or physical network disconnection. Do NOT power off (preserve volatile memory for forensics) unless active encryption is in progress.
  2. Disable compromised accounts — Force password resets for any accounts observed in lateral movement or anomalous authentication events. Revoke active sessions and tokens.
  3. Block C2 and exfiltration channels — Add known malicious IPs/domains to firewall blocklists. Temporarily restrict all outbound traffic to approved destinations only (egress filtering).
  4. Disable RDP and VPN access from external networks — If initial access vector is unconfirmed, assume edge compromise and restrict all remote access until forensic scoping is complete.
  5. Verify backup integrity — Confirm that backup infrastructure is isolated, immutable, and has not been accessed by the threat actor. Test a restore of at least one critical system.
  6. Preserve forensic evidence — Capture memory dumps, firewall/VPN logs, authentication logs, and EDR telemetry before any remediation actions overwrite evidence.
  7. Engage IR retainer / legal counsel — Activate your incident response retainer. Engage legal counsel for regulatory notification requirements (HIPAA, GDPR, state breach notification laws) based on data potentially exfiltrated.
  8. Monitor N0N's leak site — If your organization is listed or you suspect listing, monitor for data publication and prepare communications/PR response.

Hardening Recommendations

Immediate (Next 24 Hours)

These controls address the most probable initial access vectors based on N0N's known tradecraft and currently exploited CVEs:

PriorityControlRationale
P0Patch Cisco Secure FMC (CVE-2026-20316) — hard-coded password vulnerability. Verify no default credentials remain.Direct admin access to firewall management plane. CISA KEV with confirmed ransomware use.
P0Patch Check Point Security Gateway (CVE-2026-50751) — IKEv1 improper authentication. Disable IKEv1 if not operationally required.VPN gateway compromise = authenticated internal network access.
P0Patch VMware vCenter (CVE-2026-59310) — path traversal. Restrict vCenter management interface to jump hosts / management VLANs only.Hypervisor-level access enables mass VM encryption — the highest-impact ransomware outcome.
P1Disable or restrict RDP — Move RDP behind VPN, enable NLA, change from default port 3389, implement account lockout policies (5 attempts / 15-minute lockout).RDP brute force remains a top-3 initial access vector for mid-tier ransomware operations.
P1Audit all VPN accounts — Disable stale accounts, enforce MFA on all remote access, review authentication logs for anomalies in the last 90 days.Credential-based VPN access is the most common entry point when exploits are unavailable.
P1Verify shadow copy and backup integrity — Confirm VSS is functioning, backups are completing, and backup infrastructure is on a separate network segment with separate credentials.Ransomware operators target backups before encryption to eliminate recovery options.
P1Block rclone, MEGAcmd, and unauthorized cloud sync tools at the endpoint and proxy level. Alert on execution if business use exists.These are the most commonly abused exfiltration tools in double-extortion operations.
P2Patch JetBrains TeamCity (CVE-2026-63077) — deserialization RCE. Restrict TeamCity to internal networks only.CI/CD compromise enables supply-chain lateral movement into production.
P2Patch Nx Console (CVE-2026-48027) — embedded malicious code. Audit developer workstations for unauthorized extensions.Developer machine compromise yields credentials, source code, and build pipeline access.

Short-Term (Next 2 Weeks)

These are architecture-level changes that materially reduce ransomware blast radius:

ControlImplementation Detail
Network segmentation — isolate OT/ICS from ITFor energy/utilities and manufacturing organizations: implement or validate VLAN/ACL separation between operational technology and corporate IT. N0N's targeting of energy and manufacturing makes OT lateral movement a material risk.
Implement tiered administration modelSeparate Domain Admin, server admin, and workstation admin credentials. No DA logon to workstations or member servers. Deploy Privileged Access Workstations (PAWs) for all administrative functions.
Deploy LAPS for local admin passwordsEnsure every endpoint has a unique local administrator password managed by Windows LAPS or equivalent. Prevents single-credential lateral movement via Pass-the-Hash.
Enable Windows Defender Attack Surface Reduction rulesSpecifically: block Office macro child process creation, block LSASS credential dumping, block PsExec/WMI process creation from Office, block executable content from email client.
Implement egress filteringDefault-deny outbound traffic except to approved destinations. This breaks C2 communication and exfiltration for tools like rclone that depend on arbitrary outbound HTTPS.
Deploy application allowlisting on critical serversUse Windows Defender Application Control (WDAC) or AppLocker to restrict execution to approved binaries on domain controllers, backup servers, and virtualization hosts.
Enable SMB signing and disable SMBv1Prevents NTLM relay attacks used for lateral movement. SMBv1 is a legacy protocol with known exploitation vectors.
Establish out-of-band communication planPre-stage a secure communication channel (Signal group, personal email tree, printed phone list) for use during an active incident when corporate email/Teams may be encrypted or monitored by the threat actor.

Analyst Assessment

N0N's current publication cadence — 15 listings in 72 hours — represents a measurable escalation in operational tempo. The multi-sector, multi-geography spread suggests either a maturing operation with growing initial access capability or an aggressive visibility play to establish credibility in the ransomware marketplace.

The sectors being targeted — manufacturing, healthcare, energy, professional services, and technology — are consistent with organizations that hold high-value data, face regulatory disclosure requirements, and often have resource-constrained security teams. This is not random targeting. It reflects a calculated assessment of which organizations are most likely to pay.

The convergence of CISA KEV-listed vulnerabilities in edge devices (Cisco FMC, Check Point), virtualization infrastructure (VMware vCenter), and developer tooling (TeamCity, Nx Console) provides a clear defensive priority list. Organizations in the sectors represented in this campaign should treat these CVEs as active attack surface and validate patch status, segmentation, and detection coverage accordingly.

This assessment is based on unverified threat-actor claims and open-source vulnerability intelligence. It will be updated as additional information becomes available.


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.

N0N Ransomware Gang: 15 New Victims Claimed on Dark Web — Sector Analysis, Detection Rules & Response Playbook | Security Arsenal | Security Arsenal