Decoding the world of cybersecurity

N-central servers breached despite emergency patch

Attackers breached N-central servers despite a recently released emergency patch. Researchers identified 21 compromised systems, including 19 running Hotfix 2, as N-able imposed further restrictions.

N-central servers breached despite emergency patch
Summary
  • Researchers identified 21 compromised N-central servers running cryptocurrency miners, including 19 already updated to Hotfix 2.
  • The newly disclosed 4EverAble2Shell exploit chain targets installations with the Legacy API enabled; Agent2Shell presents a separate risk involving managed endpoints.
  • N-able has disabled selected integrations, issued indicators of compromise and begun developing further remediation.

Attackers have compromised N-able N-central servers already running a recent emergency security update, with researchers identifying 21 infected installations used for cryptocurrency mining across several countries, including the UK, Germany and France.

Research by security company Huntback found that 19 of the 21 compromised servers were running N-central 2026.4 Hotfix 2, released on 10 November to address an earlier collection of vulnerabilities. The attacks followed the public disclosure of an additional exploit chain on 12 November.

N-able subsequently issued new guidance, restricted some platform functionality and published indicators of compromise. The company says exploitation associated with the latest activity affects customers that have enabled its Legacy API, which is disabled by default.

N-central provides remote monitoring and management functions used by managed service providers and internal IT departments. Its administrative permissions allow operators to manage customer servers, deploy software and perform maintenance across large numbers of endpoints, increasing the potential consequences of a compromised management installation.

New exploit chain bypasses the earlier fix

Independent researcher Sean Bales disclosed two additional exploit chains on 12 November, named 4EverAble2Shell and Agent2Shell. The findings followed an earlier disclosure that prompted N-able to take hosted N-central systems offline temporarily and release Hotfix 2.

The first of the newly reported chains can provide unauthenticated remote code execution with root privileges on vulnerable N-central servers. Agent2Shell concerns weaknesses in the communications between the management server and its managed Windows devices, creating conditions in which an attacker could potentially execute commands with SYSTEM privileges.

Both findings require separate assessment. Security company eSentire has confirmed reports of exploitation of 4EverAble2Shell, while the public evidence does not establish widespread successful use of Agent2Shell against managed customer endpoints.

Huntback observed exploitation progressing from public proof-of-concept code to attacks against production infrastructure within hours. The researchers identified cryptocurrency mining activity on 21 N-central servers, with most of those installations already running the update released two days earlier.

The attackers deployed XMRig, software commonly abused to mine cryptocurrency using computing resources controlled by an unauthorised operator. The observed miner was configured to use approximately half the available processor cores, reducing the immediate performance impact that might otherwise attract attention.

Huntback located the affected systems in the United States, Canada, South Africa, the UK, Germany, France and Sweden. The 21-server total represents the researchers’ observed sample rather than a confirmed complete count of compromised N-central installations.

N-able has not provided a comprehensive customer impact total. Its own investigation identified indicators associated with environments that had left the Legacy API enabled.

Legacy functionality creates additional exposure

The Legacy API allows certain older applications and integrations to communicate with N-central. It is disabled by default, but administrators can enable it where compatibility with legacy workflows remains necessary.

That choice creates an additional attack surface. N-able says installations with the interface disabled are protected from the specific Legacy API abuse described in its latest guidance, although the company continues to investigate other authenticated and agent communication weaknesses.

Hotfix 2 addressed the internet-facing unauthenticated vulnerabilities covered by the initial disclosure. It did not resolve every issue subsequently published by the researcher, including additional problems involving legacy functionality and agent communications.

The presence of recently patched servers among the compromised systems demonstrates why patch status cannot be assessed independently of configuration. An installation may have received the latest available emergency update while retaining access to a separate interface involved in a newly disclosed exploit.

On 13 November, N-able published indicators of compromise that included suspicious file retrieval activity and network connections associated with cryptocurrency mining. The information was directed specifically towards customers that had not disabled the Legacy API.

The company also introduced precautionary restrictions affecting Microsoft Intune integration. N-able switched off the integration in hosted environments while additional safeguards were assessed and applied similar protections to affected on-premises customers where possible.

These actions can interrupt established device management workflows. Providers using N-central across multiple customer environments may therefore need to coordinate alternative processes while the restricted functionality remains unavailable.

Further fixes remain in development

N-able is developing N-central 2026.4 Hotfix 3 to address additional authenticated access weaknesses and strengthen communications between servers, Agents and Probes.

The planned update will also remove access to the Legacy API permanently, eliminating functionality that the vendor has retained for customers still using older integrations.

Hotfix 3 had not been released at the time of the company’s 13 November remediation update. Until additional corrections become available, N-able has instructed on-premises customers to keep the Legacy API disabled and follow its existing Hotfix 2 guidance.

Customers must also update Agents and Probes where required. Changes introduced by the emergency release affect how those components communicate, making version compatibility relevant both to normal management operations and to the security response.

Where attackers have already obtained root access to a management server, installing a patch does not establish that the installation is free from compromise. The observed mining activity provides evidence of unauthorised code execution, while the server’s legitimate administrative permissions create opportunities for further access if an intrusion is not contained.

The evidence published so far concerns cryptocurrency mining and compromised N-central infrastructure. It does not establish that all affected managed customer devices were compromised or that ransomware was deployed through the observed campaign.

Separate from the technical response, N-able has disputed claims that it ignored responsible vulnerability disclosure. The company says the November research was published outside its established reporting channels, and it continues to assess the findings while preparing further fixes.

By 13 November, the vendor had confirmed precautionary restrictions, published compromise indicators and outlined the additional remediation under development. The observed compromises of systems running Hotfix 2 leave configuration review and incident investigation necessary alongside installation of the available security update.

×