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
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.
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.
All times are UTC. The sequence follows public commit history and Huntback observations.
N-able released N-central 2026.4.1.26. It addresses seven previously published CVEs, not the chain disclosed two days later. [5]
Huntback observed the first check against an N-central decoy using the same SOAP endpoint and Java class as the public exploit. [2]
About 46 minutes later, the weaponised request executed as nable, escalated privileges and installed XMRig. [2]
Huntback counted 21 active nc_ miners, verified production N-central servers and identified Hotfix 2 on 19. [2]
Previdian reports 13 attempts from seven source IPs. This telemetry shows attempts, not successful access in each case. [4]
This chain reflects technical researcher findings. Indicators are defanged and no executable exploit code is included.
Attackers send a crafted SOAP request to /dms/services/ServerUI. The server chain requires the Legacy API to be enabled.
CVE-2026-90436 enables unsafe class instantiation. The named JLine class executes the supplied command.
A separate N-central flaw abuses privileged helpers and a symbolic link for privilege escalation.
In the documented attack, jup.sh downloaded XMRig, limited CPU use and established xvd.service or cron persistence.
Root on an RMM server can expose managed customer environments. Follow-on attacks have not been established.
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.
Indicators come from Huntback’s documented attack chain. IP addresses are defanged. Assess matches in context; confirmed host artefacts require incident response.
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
/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
/dms/services/ServerUI
Suspicious SOAP POST requests
jline.internal.TerminalLineSettings
exceptionName in the SOAP fault
--rig-id nc_
XMRig process command line
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]
Assessment runs only in your browser. Answers are not stored or transmitted. This check does not replace technical investigation.
Answered: 0 of 5. The assessment appears after the final answer.
Answers are neither stored nor transmitted.
This order prioritises exposure, compromise assessment and controlled recovery. Vendor guidance and internal emergency processes remain authoritative.
VamiSec CSIRT supports isolation, investigation and recovery around the clock.
This case connects vulnerability management, attack surface control, detection and customer communication. VamiSec supports the entire workflow.
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.
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.
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.
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.
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.
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.
This briefing does not replace forensic investigation or legal advice. Adapt actions to your environment and current vendor guidance.
Book a no-obligation initial call about exposure, incident response and an evidence-driven vulnerability process.