N-able N-central '4EverAble2Shell' exploit chain used to plant cryptominers on at least 21 servers, 19 of them on the 10 Nov Hotfix 2 build, Huntback says; N-able restricts features and tells on-premises customers to keep Legacy API disabled
Security researcher Sean Bales published two new N-central exploits, 4EverAble2Shell and Agent2Shell, on 12 November 2026, two days after N-able released N-central 2026.4 Hotfix 2.
According to BleepingComputer, Bales says both were tested against N-central Appliance 2026.4.1.26 HF2, that 4EverAble2Shell lets unauthenticated attackers run commands as root but needs the Legacy API to be enabled, and that Agent2Shell can run commands with SYSTEM privileges on Windows devices; BleepingComputer says 4EverAble2Shell chains an Apache Axis flaw, CVE-2026-90436, with a separate N-central privilege escalation weakness. (source: BleepingComputer)
Huntback says the proof of concept was published at 03:58 UTC on 12 November (11:58 Perth) and that from 09:16 UTC (17:16 Perth) one source, 157.20.241[.]16, ran the full chain against its N-central decoys: Apache Axis code execution as the nable user through POST /dms/services/ServerUI, escalation to root through N-central's nable_wrapper.pl helper, then installation of an XMRig Monero miner. At 12:50 UTC (20:50 Perth) the operator's public mining pool listed 21 active rigs named nc_<victim-ip>; Huntback says all 21 serve the N-central login page, 19 report build 2026.4.1.26 (Hotfix 2) and one runs 2025.3.1.9, and that they are in the United States (9), South Africa (4), Canada (4) and the United Kingdom, Germany, France and Sweden (1 each). (source: Huntback)
Previdian told BleepingComputer it saw probing of its N-central honeypot from about 08:30 UTC and later attempts to run the complete chain, with the payload contacting an attacker-controlled server at 157.20.241[.]16.
In a 12 November advisory, N-able said it is restricting certain N-central features and integrations while it develops further fixes, has disabled the Intune integration as a precaution, urged on-premises customers to make sure Legacy API access is disabled (the default), has applied the protections to hosted environments, told customers to keep upgrading Agents and Probes under the Hotfix 2 guidance, and said it had seen no signs of compromise using the new flaws. (source: N-able, according to BleepingComputer)
- Product
- N-able N-central (RMM platform for MSPs), on-premises and hosted
- Versions
- Researcher says tested against N-central Appliance 2026.4.1.26 HF2, with Legacy API enabled (per BleepingComputer). Huntback saw compromised servers on 2026.4.1.26 (19) and 2025.3.1.9 (1). N-able says further fixes are in development (per BleepingComputer, 12 Nov 2026).
- Exploited in Australia?
- unknown
- Patch to
- Per N-able (via BleepingComputer): on-premises N-central, make sure Legacy API access is disabled (the default) and keep upgrading Agents and Probes under the Hotfix 2 guidance; hosted environments already have the protections. Huntback lists checks: /tmp/.xvd or /var/tmp/.xvd, /etc/systemd/system/xvd.service or /etc/cron.d/xvd, a crontab line ending # xvkeep, a symlink at /var/opt/n-central/flag/flag_default.json, outbound connections to 157.20.241[.]16, and POSTs to /dms/services/ServerUI naming jline.internal.TerminalLineSettings. BleepingComputer says a hit should be treated as a full compromise of the server.
- Primary: Huntback — 4EverAble2Shell is already mining Monero on live N-central servers (12 Nov 2026)
- Vendor: N-able — N-central 2026.4 HF2 Release Notes (10 Nov 2026)
- CVE: CVE-2026-90436
- Source: BleepingComputer — New N-able "4EverAble2Shell" zero-day exploited hours after PoC released (12 Nov 2026; 02:51 PM EST = 03:51 AWST 13 Nov)
