Threat Overview
On November 12, 2026, public 4EverAble2Shell proof-of-concept code was followed within hours by observed exploitation against N-able N-central. Huntback documented Apache Axis code execution as nable, escalation through nable_wrapper.pl to root, and XMRig miner installation. Its observations linked 21 active mining rigs to N-central login endpoints; 19 reported build 2026.4.1.26 (Hotfix 2). This is a new chain, not simply the earlier Able2Shell disclosure. Researchers say the chain requires Legacy API enabled, which is off by default.
References
Huntback, 4EverAble2Shell miners (November 12, 2026): https://huntback.io/blog/ncentral-4everable2shell-miners-on-live-servers
N-able, N-central 2026.4 HF2 release notes (November 10, 2026): https://status.n-able.com/2026/11/10/n-central-2026-4-hf2-release-notes/
BleepingComputer, November 12 N-central exploitation: https://www.bleepingcomputer.com/news/security/
Impacted Systems
N-able N-central on-premises RMM server, including build 2026.4.1.26 (2026.4 Hotfix 2), with Legacy API enabled and reachable. The chain uses Apache Axis vulnerability CVE-2026-90436 and an additional N-central privilege-escalation weakness; a complete CVE mapping and fixed build for this new chain were not confirmed. Linux appliance/server root compromise; separately reported Agent2Shell targets managed Windows agents, but is not equivalent to the observed server chain. Hotfix 2 addresses earlier vulnerabilities but is not confirmed to stop this new chain.
Why this matters
An RMM server compromised as root can affect every managed endpoint and customer. Patch-only assurance is unsafe because researchers observed compromise on HF2.
Exploitation Status
Huntback observed active 4EverAble2Shell exploitation and miner persistence on November 12. Attacker source 157.20.241.16 is a reported campaign IOC, not proof of all attacks.
What this hunt looks for
Prepared to search the relevant available Microsoft Sentinel tables for Apache Axis request activity, N-central service account privilege escalation, XMRig miner artifacts, cron/systemd persistence and unusual outbound mining connections. No customer telemetry was actually reviewed in this run.
Required logs
Each query heading identifies its required Microsoft Sentinel data source. Execute only where that data source is ingested and retained; no customer workspace execution or findings are asserted.
N01 — N-central Apache Axis exploit request indicators
Required telemetry: CommonSecurityLog from HTTP-capable WAF/proxy/firewall with URL fields
CommonSecurityLog
| where TimeGenerated >= ago(30d)
| where RequestURL has '/dms/services/ServerUI' or Message has 'jline.internal.TerminalLineSettings'
| project TimeGenerated, DeviceName, SourceIP, DestinationIP, RequestURL, Message, DeviceAction
| order by TimeGenerated desc
N02 — N-central exploit markers in Linux Syslog
Required telemetry: Linux Syslog from N-central host or HTTP access log forwarded as Syslog
Syslog
| where TimeGenerated >= ago(30d)
| where SyslogMessage has_any ('nable_wrapper.pl','jline.internal.TerminalLineSettings','/dms/services/ServerUI','/tmp/.xvd','xvd.service','xvkeep')
| project TimeGenerated, Computer, Facility, ProcessName, SyslogMessage
| order by TimeGenerated desc
N03 — N-central root escalation or miner execution
Required telemetry: Defender for Endpoint process events from Linux N-central server, if supported and ingested
DeviceProcessEvents
| where TimeGenerated >= ago(30d)
| where ProcessCommandLine has_any ('nable_wrapper.pl','xmrig','/tmp/.xvd','/var/tmp/.xvd') or FileName =~ 'xmrig'
| project TimeGenerated, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessFileName
| order by TimeGenerated desc
N04 — N-central miner and persistence file artifacts
Required telemetry: Defender for Endpoint file events from Linux server
DeviceFileEvents
| where TimeGenerated >= ago(30d)
| where FolderPath has_any ('/tmp/.xvd','/var/tmp/.xvd','/etc/systemd/system/xvd.service','/etc/cron.d/xvd','/var/opt/n-central/flag/flag_default.json')
| project TimeGenerated, DeviceName, ActionType, FileName, FolderPath, InitiatingProcessFileName
| order by TimeGenerated desc
N05 — Attacker IP communications
Required telemetry: CommonSecurityLog from network devices
CommonSecurityLog
| where TimeGenerated >= ago(30d)
| where SourceIP == '157.20.241.16' or DestinationIP == '157.20.241.16'
| project TimeGenerated, DeviceName, SourceIP, DestinationIP, DestinationPort, DeviceAction, Message
| order by TimeGenerated desc
N06 — N-central suspicious outbound destinations
Required telemetry: Defender for Endpoint network events from N-central Linux server
let Known = DeviceNetworkEvents
| where TimeGenerated between (ago(30d) .. ago(2d))
| summarize by DeviceId, RemoteIP;
DeviceNetworkEvents
| where TimeGenerated >= ago(2d)
| where InitiatingProcessCommandLine has_any ('nable','xmrig','xvd') or InitiatingProcessFileName in~ ('xmrig','curl','wget')
| where isnotempty(RemoteIP)
| join kind=leftanti Known on DeviceId, RemoteIP
| project TimeGenerated, DeviceName, RemoteIP, RemotePort, InitiatingProcessFileName, InitiatingProcessCommandLine
| order by TimeGenerated desc
N07 — N-central cron and systemd persistence traces
Required telemetry: Linux Syslog from N-central host
Syslog
| where TimeGenerated >= ago(30d)
| where SyslogMessage has_any ('xvd.service','/etc/cron.d/xvd','# xvkeep','systemctl enable','crontab')
| project TimeGenerated, Computer, ProcessName, SyslogMessage
| order by TimeGenerated desc
Detection Notes
Highest-signal evidence: POST /dms/services/ServerUI with jline.internal.TerminalLineSettings, N-central service-account command execution, /tmp/.xvd, xvd.service and cron persistence. Standard Azure WAF tables will not cover N-central without its traffic passing through that WAF. Syslog lacks full HTTP bodies and process parent relationships; custom N-central web logs may require normalization. Absence of those logs is a visibility gap.