Get a free audit
Apple credit Apple credits the researcher who runs our AI penetration testing.

Field Notes / MSP

N-central was patched on Tuesday. By Thursday lunchtime, 21 servers were mining for someone else.

A new N-able N-central exploit chain, 4EverAble2Shell, reached root on MSP servers about five hours after the code went public. Nineteen of the first 21 victims ran the newest hotfix. What the attacker gets, the one setting that decides your exposure, and what to check today if you run N-central.

Author
Red Team Partners
Read
6 MIN READ
Filed
16 Nov 2026
A system administrator working at a laptop between server racks in a data centre.

At 03:58 UTC on Thursday 12 November, exploit code for N-able N-central landed in a public repository. At 09:16 the first server fell to it: root access, a cryptocurrency miner installed, a cron job to keep it running. By 12:50, 21 N-central servers were mining Monero for the same wallet, and 19 of them were running Hotfix 2, the update N-able had shipped two days earlier Huntback .

The chain is called 4EverAble2Shell. If you run N-central on your own server with the Legacy API switched on, the newest patch does not protect you, and N-able’s advice is to switch that API off now Tuskira .

Everything below is for MSPs. It is also for anyone whose MSP runs N-central.

01 Five hours from public code to miners

This was the second wave in a week. Earlier, researcher Sean Bales had published more than 30 N-central flaws, and N-able took its hosted N-central offline while it patched BleepingComputer . Hotfix 2 (build 2026.4.1.26) followed on 10 November with seven CVEs fixed N-able . Then came new code that worked against it.

12 Nov (UTC)What happened
03:584EverAble2Shell and Agent2Shell code published
07:48Repository updated: the chain needs the Legacy API enabled
08:30First scan for the flaw hits a decoy server
09:16First full chain: root, miner installed
12:5021 compromised N-central servers mining, 19 on Hotfix 2

The victims sat in the US (9), South Africa (4), Canada (4), and one each in the UK, Germany, France and Sweden SecurityWeek .

02 What the attacker gets

The first stage abuses Apache Axis, an old web services library inside N-central, through CVE-2026-90436, rated 9.8. Apache considers Axis 1.x finished and plans no fix Tuskira . That gives the attacker code running as N-central’s own service account. The second stage tricks a privileged helper script into running the attacker’s commands as root Huntback .

So far the crew using it wants processing power. Huntback says the miner is the only payload it has seen.

Do not take comfort from that. Root on the RMM server means the attacker holds the stored credentials, the scripts and the scheduling that reach every client you manage, and a second chain published the same morning, Agent2Shell, is described as running commands on managed Windows devices with SYSTEM privileges SecurityWeek . Nobody has reported Agent2Shell used in an attack yet. A miner crew that already has root is one sale away from a ransomware crew that knows what an RMM is for.

03 What to do today

If you are on hosted N-central, N-able applied protections on its side. If you run it yourself, work through this list before you do anything else:

  • Disable the Legacy API. It is off by default, so check whether someone switched it on for an old integration. N-able’s words: “Ensure Legacy API access is disabled in your environment” Tuskira .
  • Install Hotfix 2 anyway. It closes seven other flaws from the first wave. Upgrade agents first, then probes N-able .
  • Take the console off the open internet if you can. Put it behind a VPN or an allow-list until the next hotfix lands.
  • Watch for the follow-up hotfix. N-able has promised one and given no date BleepingComputer .

04 If your Legacy API was on

Then assume someone came in, and look for the marks this crew leaves: a .xvd folder in /tmp or /var/tmp, an xvd service or cron entry, an XMRig process with “nc_” in its rig ID, and requests to /dms/services/ServerUI in your web logs carrying a SOAP fault that names jline.internal.TerminalLineSettings Huntback . Huntback’s advice is to treat a match as a full compromise rather than a cleanup job.

Finding no miner does not clear you. The first wave of flaws had been public since early in the week, so review N-central logins, new admin accounts and new scripts from 8 November onwards, and rotate every credential N-central stores for your clients, which is what Huntress and Belgium’s national cyber centre advise Tuskira . On 13 November N-able said it had identified additional indicators of compromise SecurityWeek , so expect this list to grow.

Your clients will ask whether their environments were reachable. The honest answer comes from testing what your RMM can touch, and our partner programme does exactly that under your name, so you can answer the question before they ask it.

Questions readers ask

What is 4EverAble2Shell?

4EverAble2Shell is an exploit chain against N-able N-central, the remote monitoring and management platform many MSPs use. Proof-of-concept code went public on 12 November 2026. The first stage abuses Apache Axis (CVE-2026-90436, CVSS 9.8) to run code as the N-central service account; the second escalates to root on the server. Attackers used it within about five hours of publication.

Does N-central Hotfix 2 fix 4EverAble2Shell?

No. Hotfix 2 (build 2026.4.1.26, released 10 November 2026) fixed seven earlier CVEs, and 19 of the first 21 servers compromised with 4EverAble2Shell were running it. The chain needs the Legacy API to be enabled, so N-able’s advice is to make sure Legacy API access is disabled. N-able has promised a further hotfix.

Can attackers reach the devices N-central manages?

A second chain published the same day, Agent2Shell, is described by its author as giving SYSTEM-level command execution on managed Windows devices. As of 13 November no public source reported it being used in attacks. The server-side chain was being used, and root on the N-central server is the position from which an attacker would try to reach every client.

How do I know if my N-central server was hit?

Look for a .xvd folder in /tmp or /var/tmp, an xvd systemd service or cron entry, an XMRig process with “nc_” in its rig ID, and POST requests to /dms/services/ServerUI carrying a SOAP fault that names jline.internal.TerminalLineSettings. Huntback, which published these indicators, advises treating any match as a full compromise.

References

Sources

  1. Huntback. “4EverAble2Shell: miners on live N-central servers.” 12 November 2026. huntback.io
  2. BleepingComputer. “New N-able “4EverAble2Shell” zero-day exploited hours after PoC released.” 12 November 2026. bleepingcomputer.com
  3. SecurityWeek. “Hackers exploit new N-central zero-day hours after PoC publication.” 13 November 2026. securityweek.com
  4. N-able. “N-central 2026.4 HF2 release notes.” N-able status page, 10 November 2026. status.n-able.com
  5. Tuskira. “N-able N-central Able2Shell advisory.” Updated 12 November 2026. tuskira.ai