Zero-day · Active exploitation · Briefing

N-able N-central: 4EverAble2ShellWhen Hotfix 2 alone is not enough

Targeted attacks began within hours of the proof of concept being published. Huntback counted 21 compromised production servers – 19 running the current Hotfix 2. Our briefing explains the attack chain and what operators need to check now.

  • PoC and attacks on 12 November
  • Legacy API required
  • Root access to RMM servers
  • XMRig observed as payload

At a glance

What is established – and what is not

According to Huntback, only four and a half hours passed between the PoC and the first targeted check. Exploit claims, observed attacks and confirmed compromise must be distinguished.

  1. The server chain achieves root. It combines Apache Axis CVE-2026-90436 with a separate N-central privilege escalation.
  2. Hotfix 2 does not address everything. It fixes seven earlier CVEs but does not reliably stop this new chain.
  3. Legacy API is the key switch. The documented server chain requires it to be enabled and reachable.
  4. 21 is a point-in-time count. It comes from a mining pool on 12 November, not a final victim total.
  5. Agent2Shell is separate. Its claimed Windows SYSTEM access is not the same as the documented miner attacks.
  6. RMM increases potential impact. Root on the management server crosses a central trust boundary to managed customer systems.

Supported by researcher findings

  • Unauthenticated execution starts as nable and ends with root privileges.
  • The documented shell script installed XMRig and established persistence.
  • 19 of the 21 production servers checked reported build 2026.4.1.26, Hotfix 2.
  • Huntback verified production N-central servers rather than decoys.

Still open or limited

  • The count of 21 does not exclude additional or later cases.
  • Previdian exploitation attempts do not each prove successful access.
  • The complete affected version range has not been verified.
  • Follow-on attacks through RMM connections have not been established.
Timeline

From hotfix to same-day exploitation

All times are UTC. The sequence follows public commit history and Huntback observations.

  1. Vendor

    Hotfix 2 for earlier Able2Shell flaws

    N-able released N-central 2026.4.1.26. It addresses seven previously published CVEs, not the chain disclosed two days later. [5]

  2. Research

    4EverAble2Shell and Agent2Shell published

    Sean Bales published both PoC chains. 4EverAble2Shell targets server root; Agent2Shell targets SYSTEM privileges on managed Windows systems. [1][2]

  3. Research

    First targeted check

    Huntback observed the first check against an N-central decoy using the same SOAP endpoint and Java class as the public exploit. [2]

  4. Attack

    Full chain with root and miner

    About 46 minutes later, the weaponised request executed as nable, escalated privileges and installed XMRig. [2]

  5. Research

    21 active miners linked to N-central

    Huntback counted 21 active nc_ miners, verified production N-central servers and identified Hotfix 2 on 19. [2]

  6. Research

    Further exploitation attempts

    Previdian reports 13 attempts from seven source IPs. This telemetry shows attempts, not successful access in each case. [4]

Attack path

From a legacy interface to root

This chain reflects technical researcher findings. Indicators are defanged and no executable exploit code is included.

  1. Legacy API reachable

    Attackers send a crafted SOAP request to /dms/services/ServerUI. The server chain requires the Legacy API to be enabled.

  2. Axis processes the fault message

    CVE-2026-90436 enables unsafe class instantiation. The named JLine class executes the supplied command.

  3. From service account to root

    A separate N-central flaw abuses privileged helpers and a symbolic link for privilege escalation.

  4. Payload and persistence

    In the documented attack, jup.sh downloaded XMRig, limited CPU use and established xvd.service or cron persistence.

  5. RMM as potential launch point

    Root on an RMM server can expose managed customer environments. Follow-on attacks have not been established.

Hotfix 2 remains necessary – but is not enough

Hotfix 2 fixes seven earlier CVEs and should still be deployed with the prescribed Agent and Probe updates. 4EverAble2Shell additionally requires Legacy API to be disabled and exposure controlled.

Why a miner is not the real risk

  • N-central centrally manages numerous endpoints and customer environments.
  • Root privileges enable more than the mining payload observed so far.
  • Persistence and recovery make simply deleting the miner insufficient.
  • A confirmed hit must be treated as full server compromise.
Detection

Published IOCs and hunting guidance

Indicators come from Huntback’s documented attack chain. IP addresses are defanged. Assess matches in context; confirmed host artefacts require incident response.

Network

157.20.241[.]16
Exploit source, payload host and callback

139.99.69[.]109:10128
Primary mining pool

79.76.51[.]56:39100
Fallback mining pool

Host and persistence

/tmp/.xvd · /var/tmp/.xvd
Miner working directories

xvd.service · /etc/cron.d/xvd
Unexpected services or cron files

# xvkeep
Tagged crontab line for nable or root

Logs and processes

/dms/services/ServerUI
Suspicious SOAP POST requests

jline.internal.TerminalLineSettings
exceptionName in the SOAP fault

--rig-id nc_
XMRig process command line

Treat a hit as full compromise

Do more than delete the miner: isolate the server in a controlled way, preserve evidence, rebuild from a known-good state, rotate credentials and review RMM actions and connected customer environments. [2]

Self-check

Are the five key controls confirmed?

Assessment runs only in your browser. Answers are not stored or transmitted. This check does not replace technical investigation.

  1. Is Legacy API verifiably disabled on every N-central server you operate?
  2. Is the management interface reachable only through controlled network paths?
  3. Are Hotfix 2 and the Agent and Probe updates fully deployed?
  4. Have logs, processes, files and persistence been checked for published IOCs?
  5. Is your response to full server compromise prepared?
Your assessment

Answered: 0 of 5. The assessment appears after the final answer.

Answers are neither stored nor transmitted.

Action plan

What operators should do now

This order prioritises exposure, compromise assessment and controlled recovery. Vendor guidance and internal emergency processes remain authoritative.

Now

Close the attack surface

  • Disable Legacy API and verify the change.
  • Restrict management access to trusted networks.
  • Continue Hotfix 2 and Agent and Probe updates.
  • Monitor N-able status and further hotfix guidance.
Check

Hunt for compromise

  • Search logs for SOAP POSTs and the named JLine class.
  • Check .xvd, xvd.service, cron and nc_ miner processes.
  • Inspect connections to published IPs and pools.
  • Correlate events since 12 November with available logs.
If hit

Treat as full compromise

  • Isolate the server and preserve evidence.
  • Do not simply remove or clean the miner.
  • Start recovery and credential rotation.
  • Review RMM actions and connected customer environments.
Suspect an active incident?

VamiSec CSIRT supports isolation, investigation and recovery around the clock.

Report incident csirt@vamisec.com
How VamiSec helps

From vulnerability signal to controlled incident response

This case connects vulnerability management, attack surface control, detection and customer communication. VamiSec supports the entire workflow.

FAQ

Frequently asked questions about 4EverAble2Shell

Are all N-central installations affected?

The sources do not support this blanket statement. The documented server chain requires Legacy API to be enabled and reachable. Version, configuration and exposure must be assessed together.

Is installing Hotfix 2 enough?

Not against the new chain. Hotfix 2 addresses earlier Able2Shell CVEs and remains important. Huntback nevertheless found 19 compromised servers running that build. Legacy API must also be disabled and exposure controlled.

Is CVE-2026-90436 the entire N-central vulnerability?

No. The CVE covers the Apache Axis entry point. The chain uses a separate N-central privilege escalation, tracked by Previdian as VULN-2026-0009, to gain root.

Are the 21 servers the final victim count?

No. Huntback describes a snapshot at 12:50 UTC on 12 November: 21 active miners with nc_ identifiers in the attacker’s public pool. Additional or later cases are not excluded.

Is removing XMRig sufficient?

No. The chain gains root and establishes persistence. Confirmed hits should be treated as full server compromise, including isolation, forensic preservation, recovery and review of RMM connections.

Sources

Sources and further information

Information is based on vendor guidance, technical researcher reports and media coverage reviewed through 16 November 2026. Observations, claims and open points are identified separately.

  1. [1]BleepingComputer: New N-able “4EverAble2Shell” zero-day exploited hours after PoC released,
  2. [2]Huntback: 4EverAble2Shell is already mining Monero on live N-central servers,
  3. [3]N-able: Incident 202613: N-central security response,
  4. [4]Previdian: VULN-2026-0009: N-central 4EverAble2Shell,
  5. [5]Tenable: Able2Shell FAQ: N-able N-central Zero-Days and Hotfix 2,
  6. [6]NVD: CVE-2026-90436 · Apache Axis,

This briefing does not replace forensic investigation or legal advice. Adapt actions to your environment and current vendor guidance.

Act now

RMM needs a protected trust boundary.
We help with assessment and incident response.

Book a no-obligation initial call about exposure, incident response and an evidence-driven vulnerability process.