Within hours of a proof-of-concept release, attackers have started actively exploiting a pair of zero-day vulnerabilities in N-able N-central, a remote monitoring and management platform widely deployed by managed service providers and enterprise IT teams. Security researchers tracking the campaign have identified at least 21 compromised production servers, including 19 systems running N-able's most recent security update released on November 10. The attackers are deploying cryptocurrency miners on compromised infrastructure, though the full scope of potential damage remains unclear given the platform's privileged access to customer networks.

Security researcher Sean Bales disclosed two new zero-day exploits on November 12, naming them 4EverAble2Shell and Agent2Shell. According to Bales, these flaws permit attackers to obtain root-level access on N-central appliances and SYSTEM-level access on Windows systems. The 4EverAble2Shell vulnerability chains an Apache Axis flaw tracked as CVE-2026-90436 with a separate N-central privilege escalation weakness to achieve unauthenticated remote code execution, though the platform's Legacy API functionality must be enabled for the attack to succeed. The second exploit, Agent2Shell, targets the platform's agent component and enables command execution with elevated privileges on Windows endpoints.
The timing of these disclosures follows N-able's emergency response to earlier zero-day reports from Bales, which prompted the company to take hosted N-central environments offline and instruct on-premises customers to shut down their servers. Bales has publicly criticized N-able's response to vulnerability disclosures and the company's pace in addressing responsibly reported flaws. He stated, "It's much much easier for me to just release the research I have and the vendor can decide what they want to do with it, what they do and don't want to fix, etc. :)". Bales also noted that N-able has not patched two unrelated remote code execution vulnerabilities in a separate N-able product that he disclosed to the company in July.
In response to the new disclosures, N-able announced on November 12 that it was implementing additional protective measures while developing comprehensive patches. The company stated, "We are restricting certain N-central features and integrations. These measures may affect some functionality, but we believe taking additional precautions while remediation is completed is the right action to protect our partners and their customers." N-able has disabled the Intune integration as a precautionary step and is directing on-premises customers to verify that Legacy API access remains disabled, which is the default configuration. These protections have already been deployed to hosted environments, and customers are advised to continue upgrading their Agents and Probes according to previous guidance.
Exploitation Already Underway in the Wild
Cybersecurity firm Previdian documented that threat actors began probing for the 4EverAble2Shell vulnerability on November 12, shortly after Bales published the proof-of-concept code. The company's honeypot systems detected suspicious requests at approximately 08:30 UTC, using the same Java class components referenced in the public exploit. Initial reconnaissance activity evolved into attempts to execute the complete exploit chain, mirroring the attack sequence Bales released on GitHub.
The exploitation technique follows a two-stage process. Attackers first leverage Apache Axis CVE-2026-90436 to execute commands under the 'nable' service account, then exploit N-central's privileged setLDFileOwner helper function combined with symbolic link manipulation to make a normally root-owned script writable. The attacker modifies this script and invokes N-central's serverControl functionality to execute commands with root privileges, then attempts to restore the altered files to avoid detection. Previdian has assigned the privilege escalation component the tracking identifier VULN-2026-0009 and added it to its Known Exploited Vulnerabilities catalog.
Cybersecurity company Huntback confirmed that attackers have successfully compromised at least 21 production N-central servers using the publicly available exploit chain. Huntback observed the same attacker IP address as Previdian probing its honeypots at approximately 08:30 UTC on November 12, with the first complete exploit attempts beginning at 09:16 UTC. The attacks downloaded and executed shell scripts that installed XMRig, a Monero cryptocurrency miner configured to consume approximately half of available CPU resources, likely to reduce detection likelihood.
Huntback identified the compromised systems through the attacker's cryptocurrency mining pool, where infected servers were assigned identifiers following the pattern nc_ followed by the server's IP address. At 12:50 UTC on November 12, researchers identified 21 active miners using this naming scheme, all having submitted mining shares within the preceding five minutes. Verification of the associated IP addresses confirmed that all 21 hosted N-central installations were compromised, with 19 running version 2026.4.1.26, the latest Hotfix 2 release. The affected servers span multiple geographic regions, including the United States, Canada, South Africa, the United Kingdom, Germany, France, and Sweden.
While observed attacks have focused on cryptojacking, the full root access granted by 4EverAble2Shell creates significant risk for broader compromise. Attackers could leverage compromised N-central infrastructure to target the managed customer environments that depend on these platforms for monitoring and control.
Detection and Response Guidance
Organizations operating N-central should verify that Legacy APIs are disabled and monitor for suspicious requests to /dms/services/ServerUI, particularly those containing references to jline.internal.TerminalLineSettings. Huntback recommends investigating the presence of unexpected xvd.service systemd services, cryptocurrency mining processes, and files created under /tmp/.xvd or /var/tmp/.xvd.
Given that 4EverAble2Shell exploitation results in complete root access to affected servers, organizations that detect these indicators of compromise should treat the incident as a full server compromise and initiate comprehensive incident response procedures.