N-central mined via 4EverAble2Shell — 19 of 21 were patched
A new N-central exploit chain, 4EverAble2Shell, plants XMRig on 21 servers within hours of PoC release; 19 were running Hotfix 2. Applying the hotfix alone did not stop it.
A second N-able N-central exploit chain, 4EverAble2Shell, went from proof-of-concept to active exploitation within hours of release, and the servers it hit were mostly patched. Huntback tied a single attacker host to 21 compromised N-central servers running the XMRig Monero miner — and 19 of the 21 were already on Hotfix 2. Reported by The Hacker News from Huntback's research. If you self-host N-central, the hotfix was not the finish line.
What's affected
Independent researcher Sean Bales published two new chains, 4EverAble2Shell and Agent2Shell, on November 12 — a follow-up to the earlier Able2Shell release we covered when N-able pulled its hosted cloud. 4EverAble2Shell's first stage is CVE-2026-90436 (CVSS 9.8), a critical flaw in the end-of-life Apache Axis 1.x component N-central ships, chained with an N-central privilege-escalation weakness to reach root on the host. No single CVE covers the full chain.
Exploitation status
Confirmed. Huntback reports the 4EverAble2Shell PoC was weaponized within hours of its November 12 release — one honeypot logged a complete chain the same day. Only XMRig has been seen so far; the miner is capped at roughly half the available CPU cores to stay under the radar, with persistence via systemd or cron. Agent2Shell, released alongside, has not been observed in attacks. Compromised servers cluster in the US, South Africa, Canada, the UK, Germany, France and Sweden. Huntback's line is blunt: "Applying Hotfix 2 is not enough on its own" — treat any hit as a full host compromise.
Indicators
From Huntback and The Hacker News, verbatim:
URLs:
157.20.241[.]16:8080/jup.sh
157.20.241[.]16:8080/xvgz
157.20.241[.]16:8080/xmrig.tgz
157.20.241[.]16:8080/ob/cronhit?h=jup_start_<rig>&persist=<method>
157.20.241[.]16:8080/ob/fcheck
Outbound:
157.20.241[.]16 (ports 8080, 19202-19418)
139.99.69[.]109:10128
79.76.51[.]56:39100
Action checklist
- Disable the Legacy API on on-premises N-central — it is the targeted surface, and it is off by default only in hosted environments.
- Upgrade Agents and Probes to N-central 2026.4 HF1 and above, per N-able's guidance, and apply the latest hotfix to the server itself.
- Treat a confirmed hit as a full compromise, not a cleanup: a patched build was not protective here. Hunt the indicators above, check for unexpected CPU load, and rebuild rather than remove-and-move-on.
- Block the IOC infrastructure above at the egress firewall.
Context
N-central runs privileged agents across every endpoint an MSP manages, so root on the server is a path to downstream customers — the same reason the August N-central exploitation wave drew a CISA KEV listing. The uncomfortable detail this time is that 19 of 21 victims had applied Hotfix 2. A patched asset compromised through an EOL dependency is the kind of gap a hotfix cycle does not close on its own.