Researchers report at least 21 compromised N-able N-central servers, including patched systems, as attackers used a newly published exploit chain to install cryptocurrency miners.
Attackers reportedly began exploiting a newly disclosed vulnerability chain in N-able’s N-central remote-management software within hours of proof-of-concept code appearing online. Security researchers say at least 21 servers were compromised and used to run cryptocurrency-mining software, including systems that had received N-able’s latest patches.
The incident matters beyond the miners themselves. N-central is used to manage customer devices, and researchers say the exploit chain can give an attacker root access to the server. A compromised management system can put the endpoints under its control at risk, making this a potential operational and customer-security incident—not simply an unwanted use of computing power.
The exploit, dubbed 4EverAble2Shell, was published by security researcher Sean Bales on November 12. SecurityWeek reported that the chain combines an Apache Axis vulnerability, CVE-2026-90436, with a separate weakness in N-central deployments where Legacy API is enabled. The published code reportedly targets Axis for remote code execution, then seeks to elevate privileges and run a shell script.
Previdian described the escalation mechanism as abuse of N-central’s privileged `setLDFileOwner` helper and a symbolic link to make a root-owned script writable. The chain then uses `serverControl` to execute commands as root. Previdian assigned the issue the identifier VULN-2026-0009 and added it to its Known Exploited Vulnerabilities catalog. WatchTowr separately reported probes against N-central builds with Legacy API enabled.
Early reports of probing did not, on their own, establish successful compromise. Lupovis and Huntback later told SecurityWeek they observed successful exploitation roughly five hours after the code was released. Lupovis linked 21 miner rigs to compromised servers in the United States, South Africa, Canada, the United Kingdom, Germany, France and Sweden. Huntback said 19 victims were running N-able’s latest patches, including build 2026.4.1.26.
The attackers installed XMRig cryptocurrency miners and used systemd or cron to keep them running. Researchers also identified attempts to download and execute a shell script from `157.20.241[.]16`. Other indicators include requests to `/dms/services/ServerUI` referencing `jline.internal.TerminalLineSettings`, unexpected `xvd.service` units, and `.xvd` files in `/tmp` or `/var/tmp`.
N-able’s stated immediate mitigation is configuration-based, not a new fixed build: the company says Legacy API is disabled by default and urges on-premises customers to disable it immediately. Hosted environments were not affected, according to N-able. Security.io reported on November 12 that no additional fixed build had been published by its reporting cutoff. N-able also said it had identified further indicators of compromise and was working with affected customers. Its response included restricting certain N-central features and integrations, including Legacy API and Intune integration.
For small IT teams, disabling Legacy API should be the first step on any on-premises N-central installation where it remains enabled. Teams should then check the listed network, file and service indicators, review authentication and administrative activity, and inspect systems for miner processes or persistence mechanisms. A matching indicator—or unexplained root-level activity—should be treated as a possible full server compromise. Isolating the server and escalating to N-able or incident-response specialists is safer than deleting the miner and returning the system to service.
Teams should also confirm which N-central systems are exposed and whether they are hosted or on-premises, preserve logs and evidence, and verify that endpoint-management credentials and other secrets accessible from a suspect server have not been abused. The reports show why patch status alone is not enough: defenders must address the Legacy API configuration and investigate for signs of intrusion even on systems running the latest build.

