Back to Intelligence

N-central 2026.4 HF3 Patch: Detecting & Blocking Active Cryptominer Exploitation on N-able RMM

SA
Security Arsenal Team
November 17, 2026
9 min read

N-able has issued an urgent security update for its N-central Remote Monitoring and Management (RMM) and Unified Endpoint Management (UEM) platform. The update, designated as N-central 2026.4 Hotfix 3 (HF3), addresses a cluster of 17 critical security vulnerabilities. This release is not a routine maintenance patch; it is a direct response to active exploitation observed in the wild.

Threat actors have been leveraging previously disclosed vulnerabilities in N-central to compromise the RMM platform. Once inside, they are deploying cryptocurrency miners (cryptominers). Because RMM tools like N-central operate with high privileges and deep visibility across managed endpoints, a compromise here represents a significant supply-chain risk. It provides attackers with a foothold into the networks of Managed Service Providers (MSPs) and their downstream clients.

The severity is high. RMM platforms are high-value targets because they are trusted by the operating system, often bypass application whitelisting, and have agents deployed on thousands of endpoints. Defenders must treat this as an emergency patching scenario. If your organization utilizes N-central 2026.4, immediate verification of the Hotfix 3 installation is mandatory. Failure to patch leaves the management console open to unauthorized access and the potential for widespread lateral movement.

Technical Analysis

Affected Products and Versions

The primary focus of this advisory is N-central 2026.4. The fix is delivered via Hotfix 3 (HF3). While the summary explicitly names this version, the nature of RMM vulnerabilities often implies that prior versions may share similar codebase weaknesses. Administrators running older versions of N-central should consult the vendor advisory immediately to determine if their specific build is vulnerable or requires an upgrade to 2026.4 before applying HF3.

Vulnerability Details and Exploitation

The news summary indicates that N-able is addressing "17 critical security flaws." While specific CVE identifiers for these new fixes were not explicitly listed in the provided summary, the context confirms that attackers are exploiting security issues within the platform to achieve code execution.

The attack chain typically follows this pattern:

  1. Initial Access: Attackers identify an unpatched N-central server exposed to the internet or accessible via compromised credentials.
  2. Exploitation: They leverage one of the 17 vulnerabilities (likely related to authentication bypass, insecure deserialization, or command injection within the web management interface or API) to execute arbitrary code on the N-central server.
  3. Payload Deployment: Once code execution is achieved on the server, the attackers deploy cryptominers. These miners may run directly on the N-central host (consuming server resources) or be pushed to managed endpoints via the RMM's own deployment mechanisms.
  4. Persistence: Cryptominers often establish persistence via scheduled tasks, services, or registry run keys to survive reboots.

Exploitation Status

This is confirmed active exploitation. The summary explicitly states that "Attackers security issue Earlier Bugs to Deploy Crypto Miners." This indicates that the threat actors are already weaponizing these vulnerabilities. The motivation is financial (cryptojacking), but the access gained could easily be sold to ransomware affiliates or used for espionage. There is no indication that these specific flaws are currently listed in the CISA Known Exploited Vulnerabilities (KEV) catalog yet, but the active exploitation status warrants treating them with the same urgency as a KEV entry.

Detection & Response

Given the technical nature of this threat (RCE leading to cryptomining), the following detection content is provided to hunt for signs of compromise. These detections focus on the behaviors associated with RMM abuse and cryptominer deployment.

SIGMA Rules

The following Sigma rules are designed to detect suspicious process execution and command-line arguments commonly associated with cryptominers and RMM exploitation. These rules assume the N-central server is running Windows (common for on-premise deployments) or that logs are ingested from endpoints.

YAML
---
title: N-central Suspicious Process Spawn
description: Detects the N-central server process spawning unexpected command shells or scripting engines, indicative of post-exploitation activity.
logsource:
  category: process_creation
  product: windows
detection:
  selection_parent:
    ParentImage|endswith:
      - '\ncentral.exe'
      - '\ncentral-server.exe'
      - '\n-central.exe'
  selection_child:
    Image|endswith:
      - '\cmd.exe'
      - '\powershell.exe'
      - '\wscript.exe'
      - '\cscript.exe'
      - '\mshta.exe'
      - '\rundll32.exe'
  condition: selection_parent and selection_child
falsepositives:
  - Legitimate administrative scripts executed via N-central (tune based on your environment's baseline).
level: high
---
title: Cryptominer Process Execution
description: Detects common cryptominer process names and command-line arguments often deployed after RCE.
logsource:
  category: process_creation
  product: windows
detection:
  selection_img:
    Image|endswith:
      - '\xmrig.exe'
      - '\xmr-stak.exe'
      - '\minerd.exe'
      - '\cgminer.exe'
      - '\bfgminer.exe'
      - '\ethminer.exe'
      - '\nicehashminer.exe'
  selection_cmd:
    CommandLine|contains:
      - '--donate-level'
      - '--coin'
      - '--algo'
      - 'stratum+tcp'
      - 'stratum+ssl'
      - '--pool'
      - '--wallet'
  condition: 1 of selection_*
falsepositives:
  - Legitimate mining operations (rare in corporate environments).
level: critical
---
title: Suspicious PowerShell Download Cradle
description: Detects PowerShell downloading payloads, a common technique for delivering cryptominers after initial exploitation.
logsource:
  category: process_creation
  product: windows
detection:
  selection:
    Image|endswith: '\powershell.exe'
    CommandLine|contains:
      - 'IEX'
      - 'Invoke-Expression'
      - 'DownloadString'
      - 'DownloadFile'
      - 'Start-BitsTransfer'
      - 'curl'
      - 'wget'
  filter:
    CommandLine|contains:
      - 'N-central'
      - 'ncentral'
  condition: selection and not filter
falsepositives:
  - Legitimate software deployment scripts.
level: high

KQL (Microsoft Sentinel / Defender)

This KQL query hunts for devices communicating with known mining pool ports or exhibiting suspicious process lineage involving the N-central agent. It assumes you are ingesting logs via Microsoft Defender for Endpoint or a Syslog/CEF connector.

KQL — Microsoft Sentinel / Defender
// Hunt for N-central related processes spawning suspicious children or connecting to mining ports
let MiningPorts = dynamic([3333, 4444, 5555, 7777, 8888, 9999, 14444, 45700]);
let SuspiciousProcesses = dynamic(["xmrig.exe", "minerd.exe", "cgminer.exe", "powershell.exe", "cmd.exe"]);
// Check DeviceProcessEvents for suspicious lineage
DeviceProcessEvents
| where TimeGenerated > ago(24h)
| where InitiatingProcessFileName has_any ("ncentral", "n-central") or FileName has_any ("ncentral", "n-central")
| where FileName has_any (SuspiciousProcesses) or ProcessCommandLine has_any ("stratum", "donate-level", "algo")
| project TimeGenerated, DeviceName, InitiatingProcessFileName, FileName, ProcessCommandLine, SHA256, AccountName
| join kind=leftouter (
    DeviceNetworkEvents
    | where TimeGenerated > ago(24h)
    | where RemotePort in (MiningPorts)
    | project DeviceName, RemoteIP, RemotePort, TimeGenerated
) on DeviceName
| summarize by DeviceName, InitiatingProcessFileName, FileName, ProcessCommandLine, RemoteIP, RemotePort

Velociraptor VQL

This VQL artifact hunts for processes with names or command lines matching cryptominer signatures across the endpoint fleet. This is useful for identifying if the N-central agent was used to push miners to managed devices.

VQL — Velociraptor
-- Hunt for Cryptominer Processes and Network Connections
SELECT Pid, Name, CommandLine, Exe, Username, CreateTime, Netstat.LocalIP, Netstat.LocalPort, Netstat.RemoteIP, Netstat.RemotePort, Netstat.Status
FROM pslist()
LEFT JOIN netstat() ON Pid = netstat().Pid
WHERE 
  Name =~ '(?i)(xmrig|minerd|cgminer|ethminer|xmr-stak)'
  OR CommandLine =~ '(?i)(stratum\+tcp|stratum\+ssl|donate-level|coinhive|monero)'
  OR Netstat.RemotePort IN (3333, 4444, 5555, 7777, 8888, 9999)

Remediation Script

The following PowerShell script can be run on the N-central server (if Windows-based) or deployed via the RMM itself to managed endpoints to detect and remove common cryptominer artifacts. Note: This script is a defensive measure. It terminates known miner processes, removes persistence mechanisms, and checks for suspicious scheduled tasks. Use with caution and test in a lab environment first.

PowerShell
# Define known cryptominer process names
$MinerProcesses = @("xmrig", "xmr-stak", "minerd", "cgminer", "bfgminer", "ethminer", "nicehashminer", "nheqminer")

# Function to kill miner processes
function Remove-MinerProcesses {
    foreach ($proc in $MinerProcesses) {
        $process = Get-Process -Name $proc -ErrorAction SilentlyContinue
        if ($process) {
            Write-Host "[+] Found and terminating process: $($process.Name) (PID: $($process.Id))" -ForegroundColor Yellow
            Stop-Process -Id $process.Id -Force -ErrorAction SilentlyContinue
        }
    }
}

# Function to remove common persistence locations
function Remove-MinerPersistence {
    # Registry Run Keys
    $RegPaths = @(
        "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Run",
        "HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\Run",
        "HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Run"
    )
    
    foreach ($path in $RegPaths) {
        if (Test-Path $path) {
            $items = Get-ItemProperty -Path $path
            foreach ($item in $items.PSObject.Properties) {
                foreach ($miner in $MinerProcesses) {
                    if ($item.Value -like "*$miner*") {
                        Write-Host "[+] Removing registry persistence: $($item.Name) from $path" -ForegroundColor Yellow
                        Remove-ItemProperty -Path $path -Name $item.Name -ErrorAction SilentlyContinue
                    }
                }
            }
        }
    }

    # Scheduled Tasks
    $tasks = Get-ScheduledTask | Where-Object {$_.TaskName -match ($MinerProcesses -join "|")}
    foreach ($task in $tasks) {
        Write-Host "[+] Disabling and removing scheduled task: $($task.TaskName)" -ForegroundColor Yellow
        Disable-ScheduledTask -TaskName $task.TaskName -ErrorAction SilentlyContinue
        Unregister-ScheduledTask -TaskName $task.TaskName -Confirm:$false -ErrorAction SilentlyContinue
    }
}

# Function to check for suspicious network connections
function Check-MinerConnections {
    $connections = Get-NetTCPConnection | Where-Object { $_.RemotePort -in @(3333, 4444, 5555, 7777, 8888, 9999) }
    foreach ($conn in $connections) {
        $proc = Get-Process -Id $conn.OwningProcess -ErrorAction SilentlyContinue
        Write-Host "[!] Suspicious connection detected: $($proc.Name) (PID: $($proc.Id)) connecting to $($conn.RemoteAddress):$($conn.RemotePort)" -ForegroundColor Red
    }
}

# Execute functions
Write-Host "Starting Cryptominer Cleanup Script..." -ForegroundColor Cyan
Remove-MinerProcesses
Remove-MinerPersistence
Check-MinerConnections
Write-Host "Cleanup complete. Please review any red flags above." -ForegroundColor Cyan

Remediation

Immediate action is required to secure N-central infrastructure.

  1. Apply Hotfix 3 Immediately: Download and install N-central 2026.4 Hotfix 3 from the official N-able support portal. Verify the installation by checking the version number in the N-central console.
  2. Review Vendor Advisory: Consult the official N-able security advisory for detailed release notes and specific CVE mappings. URL: https://www.n-able.com/security-advisories (Note: Navigate to the specific advisory for 2026.4 HF3).
  3. Hunt for Compromise: Do not assume patching removes existing implants. Run the detection queries and scripts provided above on the N-central server and all managed endpoints. Look for unauthorized user accounts in the N-central console, unexpected scheduled tasks, and high CPU usage.
  4. Network Segmentation: Ensure the N-central server is not directly exposed to the internet. Place it behind a VPN or a zero-trust gateway. Restrict inbound access to the management console to authorized IP addresses only.
  5. Credential Hygiene: Enforce Multi-Factor Authentication (MFA) for all N-central administrative accounts. Reset credentials for any accounts that may have been exposed.
  6. Monitor Resource Usage: Cryptominers consume significant CPU/GPU resources. Implement alerting for abnormal resource utilization spikes on the N-central server and critical endpoints.
  7. Update Agent Software: Ensure that all N-central agents deployed to endpoints are updated to the latest version compatible with 2026.4 HF3 to prevent exploitation via the agent communication channel.

Related Resources

Security Arsenal Managed SOC Services AlertMonitor Platform Book a SOC Assessment soc-mdr Intel Hub

Is your security operations ready?

Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.