CriticalCVE-2026-90436 5 Hunt LeadsIOCsRemote AttackerXMRigBleepingComputer

N-central’s New Patch Lasted Two Days: 4EverAble2Shell Is Mining Monero

A new public exploit, 4EverAble2Shell, gives root on N-central even after Hotfix 2 when the Legacy API is on. Huntback found 21 MSP servers mining Monero within hours, 19 fully patched.

N-able’s emergency N-central patch held for about two days. On Nov. 12 researcher Sean Bales published two new exploits, 4EverAble2Shell and Agent2Shell, that work against the 2026.4 Hotfix 2 N-able shipped on Nov. 10. BleepingComputer reports attackers were using the first one within hours. Huntback counted 21 production N-central servers turned into Monero miners by that afternoon, 19 of them fully patched.

For defenders

The chain: 4EverAble2Shell gets unauthenticated root on the N-central appliance when the Legacy API is enabled. Step one is CVE-2026-90436 (CVSS 9.8), a SOAP-fault deserialization bug in Apache Axis 1.x, which is end of life and won’t get a fixed release. A POST /dms/services/ServerUI with a crafted exceptionName (seen in the wild: jline.internal.TerminalLineSettings) runs commands as the nable service account (T1190 (Exploit Public-Facing Application)). Step two, which Previdian tracks as VULN-2026-0009, abuses N-central’s own nable_wrapper.pl setLDFileOwner helper through a symlink to take over a root script, then runs it with serverControl (T1068 (Exploitation for Privilege Escalation)). Agent2Shell, the second exploit, is claimed to give SYSTEM on managed Windows devices. We haven’t seen it reported in attacks yet.

In the wild: per Previdian and Huntback, probes from 157.20.241[.]16 started around 08:30 UTC on Nov. 12, about four and a half hours after the PoC went up, and full exploit attempts followed from 09:16 UTC. The root command pulls jup.sh, which installs XMRig in /tmp/.xvd on half the CPU cores and keeps it alive with an xvd.service systemd unit or a cron job (T1496.001 (Resource Hijacking: Compute Hijacking), T1543.002 (Create or Modify System Process: Systemd Service)). The same wallet had 631 mining rigs. Huntback says the operator also mines on hacked Jpom, FreePBX, MLflow, Flink and PaperCut servers. The CISA KEV list doesn’t include either bug yet. Our CVE data shows one public PoC repository.

Network
157.20.241[.]16 (exploitation source, payload host :8080, callbacks on TCP 19202-19418)
hxxp://157.20.241[.]16:8080/jup.sh
139.99.69[.]109:10128 (mining pool)
79.76.51[.]56:39100 (fallback mining endpoint)

Host
/tmp/.xvd/ or /var/tmp/.xvd/ (x, keep.sh, xm.log)
/etc/systemd/system/xvd.service, /etc/cron.d/xvd, crontab line ending “# xvkeep”
/var/opt/n-central/tmp/serverchild-*.bak|.sh|.out
symlink at /var/opt/n-central/flag/flag_default.json
miner command line containing –rig-id nc_

What it means for you

N-central is what many IT support companies use to look after their clients’ computers. If an outside firm manages your company’s PCs, it’s worth asking them this week whether they run N-central and whether they’ve checked their server. So far the attackers have only mined crypto. With the same root access they could push anything to every computer the server manages.

Do this now

  1. Disable the Legacy API on N-central now. Huntback says Hotfix 2 alone didn’t stop this.
  2. Follow N-able’s latest guidance, and keep the server off the open internet until a fix for 4EverAble2Shell ships.
  3. Check for the files, services and connections listed above, and look for a CPU-hungry process you don’t recognize.
  4. If you find any, treat the whole server as compromised: rebuild it, rotate every credential it holds, and review what it pushed to managed devices.

Source article: New N-able “4EverAble2Shell” zero-day exploited hours after PoC released
Publisher: BleepingComputer
Published: Nov. 12, 2026
URL: https://www.bleepingcomputer.com/news/security/new-n-able-4everable2shell-zero-day-exploited-hours-after-poc-released/

Executive Summary

A financially motivated cryptomining operator, not tied to any named group, began exploiting N-able N-central servers within hours of researcher Sean Bales publishing the 4EverAble2Shell and Agent2Shell exploits on Nov. 12, 2026, two days after N-able shipped N-central 2026.4 Hotfix 2 (build 2026.4.1.26) for an earlier batch of Bales disclosures. 4EverAble2Shell gives unauthenticated root on the N-central appliance when the Legacy API is enabled: it uses CVE-2026-90436, a SOAP fault deserialization flaw in the end-of-life Apache Axis 1.x library, through POST requests to /dms/services/ServerUI to run commands as the nable service account, then escalates to root with an N-central weakness Previdian tracks as VULN-2026-0009, in which the privileged nable_wrapper.pl setLDFileOwner helper follows a symlink planted at /var/opt/n-central/flag/flag_default.json and hands the root-run ServerChild.sh script to nable, which is rewritten and executed through serverControl and then restored. Previdian and Huntback both saw probes from 157.20.241[.]16 from about 08:30 UTC and full chains from 09:16 UTC; the root command fetches jup.sh, which installs XMRig under /tmp/.xvd on half the CPU cores, names each rig nc_ plus the victim’s IP, beacons to the payload host and persists through an xvd.service systemd unit or cron. By 12:50 UTC Huntback counted 21 live N-central miners across seven countries, 19 on Hotfix 2, within a wallet of 631 rigs that also covers hacked Jpom, FreePBX, MLflow, Flink, PaperCut, SFTPGo and AJ-Report servers. The observed objective is mining, but every N-central server holds remote-management access to the customers behind it, so the impact of root on it is potentially far wider. Hunt leads, false positive expectations and indicators are detailed below; no detection rules were published.

ATT&CK chain: Initial Access → Execution → Privilege Escalation → Defense Evasion → Persistence → Command and Control → Impact

Hunt Lead Grid

Hunt Lead Level Hunt Lead Name ATT&CK Risk of False Positives
1 (Junior) Operator Payload Host, Callbacks and Mining Endpoints T1105 (Ingress Tool Transfer), T1496.001 (Resource Hijacking: Compute Hijacking) Low. An N-central server has no reason to talk to these addresses; the lead anchors on the specific hosts and ports the researchers published.
1 (Junior) .xvd Miner Files, Persistence and Escalation Leftovers T1543.002 (Create or Modify System Process: Systemd Service), T1053.003 (Scheduled Task/Job: Cron) Low. The names (.xvd, xvd.service, # xvkeep, serverchild-*.bak) are operator choices; the only overlap is a legitimate flag_default.json, which is normally a regular file rather than a symlink.
2 (Pro) Axis SOAP Fault exceptionName POSTs to ServerUI T1190 (Exploit Public-Facing Application) Low. Clients send requests, not SOAP faults, to /dms/services/ServerUI; a request body carrying a Fault with an exceptionName element has no legitimate use, so the lead anchors on that structure rather than on the URL.
2 (Pro) nable_wrapper setLDFileOwner Followed by serverControl T1068 (Exploitation for Privilege Escalation) Medium. N-central maintenance legitimately calls nable_wrapper.pl; the lead anchors on the pairing of setLDFileOwner and serverControl noop –wait from a process tree under the web service, and on changes to ServerChild.sh ownership.
3 (Elite) Raw TCP Callback and CPU-Capped Miner from the nable Account T1059.004 (Command and Scripting Interpreter: Unix Shell), T1496.001 (Resource Hijacking: Compute Hijacking) Medium. N-central runs Java and helper scripts as nable all the time; the lead joins a shell under the web stack using /dev/tcp or python3 from stdin with outbound connections to non-baselined hosts and a new long-running process holding a steady share of CPU.

Operator Payload Host, Callbacks and Mining Endpoints

Huntback and Previdian both observed the same source, 157.20.241[.]16, probing N-central honeypots from about 08:30 UTC on Nov. 12 and sending the full chain from 09:16 UTC with the user-agent python-requests/2.31.0. That address also served the installer at hxxp://157.20.241[.]16:8080/jup.sh, the miner at /xvgz with /xmrig.tgz (stock XMRig 6.26.0) as fallback, and the check-in beacons /ob/cronhit and /ob/fcheck, and it received each request’s command output on raw TCP callbacks on ports 19202 to 19418. The miner then connects to 139.99.69[.]109:10128 and falls back to 79.76.51[.]56:39100 if the first does not answer within six seconds. The detection logic is a retrospective search of firewall, proxy and web logs for any connection to or from these addresses, any request carrying that user-agent to the N-central web interface, and any outbound connection from the N-central server to a TCP port in the 19202 to 19418 range.

Use perimeter firewall logs, NetFlow, egress proxy logs and the N-central server’s own Apache or Tomcat access logs. Search from Nov. 12, 2026 to now, and keep the addresses on a watchlist since the operator reuses infrastructure across exploits. Scope to every N-central server, cloud-hosted or on premises, and to the networks of any MSP managing your devices. These are single addresses that will age, so a clean result does not clear a server that had the Legacy API exposed; pair this lead with the file and persistence sweep. Blocking the addresses is cheap and sensible but does not remove the access path. Any outbound hit from an N-central server is evidence of successful exploitation and should be escalated as a full root compromise.

Hunt Lead Level: 1 (Junior Analyst)

ATT&CK: Command and Control → T1105 (Ingress Tool Transfer); Impact → T1496.001 (Resource Hijacking: Compute Hijacking)

Sources: “New N-able “4EverAble2Shell” zero-day exploited hours after PoC released”, BleepingComputer, Nov. 12, 2026, https://www.bleepingcomputer.com/news/security/new-n-able-4everable2shell-zero-day-exploited-hours-after-poc-released/ (source article); “4EverAble2Shell is already mining Monero on live N-central servers”, Huntback, Nov. 12, 2026, https://huntback.io/blog/ncentral-4everable2shell-miners-on-live-servers (additional source, same campaign)

.xvd Miner Files, Persistence and Escalation Leftovers

The jup.sh installer works from /tmp/.xvd, or /var/tmp/.xvd if /tmp is unusable, remounting /tmp with exec when it runs as root, and leaves the miner binary x, the watchdog keep.sh and the log xm.log there. It persists the watchdog, which relaunches the miner every 10 minutes if it dies, through a systemd unit /etc/systemd/system/xvd.service if it can write there, otherwise a user crontab line tagged # xvkeep, otherwise /etc/cron.d/xvd. The escalation stage is designed to clean up after itself, but Huntback lists what can survive: serverchild-*.bak, serverchild-*.sh or serverchild-*.out files in /var/opt/n-central/tmp/ and a symlink at /var/opt/n-central/flag/flag_default.json. The detection logic is a host sweep for those paths, units and crontab tags, plus a check of whether flag_default.json is a symlink and whether /tmp is currently mounted exec on an appliance that normally mounts it noexec.

Run the sweep over SSH or your configuration management tool on every N-central appliance, including systemctl list-unit-files, crontab -l for nable and root, and ls -la on the flag directory. File system state is the evidence here, so there is no lookback window; but capture it before rebuilding or rebooting, since /tmp may be cleared. Scope to all N-central servers regardless of whether the Legacy API is now disabled, because exploitation may predate the change. False positives are unlikely beyond a vendor-created flag file that is a regular file, which the symlink check separates. Deleting the .xvd folder and the unit is the wrong end state: the operator had root and a callback channel, so any hit means a rebuild from known-good media and rotation of every credential the server holds, followed by a review of what the server pushed to managed endpoints.

Hunt Lead Level: 1 (Junior Analyst)

ATT&CK: Persistence → T1543.002 (Create or Modify System Process: Systemd Service); Persistence → T1053.003 (Scheduled Task/Job: Cron)

Sources: Huntback (above), additional source, same campaign; BleepingComputer (above), source article

Axis SOAP Fault exceptionName POSTs to ServerUI

CVE-2026-90436 lets an unauthenticated client send a SOAP Fault whose detail element names an arbitrary Java class in exceptionName; Apache Axis 1.x loads that class, running its static initializer, and, if a String data element is present, instantiates it through its String constructor, all before any per-service authentication handler runs. In 4EverAble2Shell the requests go to POST /dms/services/ServerUI, and both Previdian and Huntback saw the class jline.internal.TerminalLineSettings in the exceptionName element, with the operator’s command carried in the data field: a shell line that takes a flock on /var/opt/n-central/tmp, base64-decodes a Python script into python3 and returns output over /dev/tcp. The detection logic is a request-body rule at the web tier or IDS: alert on any POST to /dms/services/ (and other Axis 1.x endpoints) whose body contains a soapenv:Fault with a detail/exceptionName element, and at critical severity when the class is jline.internal.TerminalLineSettings or the data element contains shell or base64 content.

Use a WAF or reverse proxy in front of N-central with request-body logging enabled, or network IDS with HTTP body inspection, since default access logs show only the path. Review whatever body logs exist back to Nov. 6, 2026, when the Axis CVE was published. Scope to N-central servers first, then to any other internal application that bundles Axis 1.x, because the bug is in the library and Axis will not get a fixed release. Do not alert on the path alone, which normal N-central clients use. Blocking the jline class name is a weak control since other classpath gadgets exist; disabling the Legacy API and removing internet exposure are the durable fixes. Any matching request that received a 200 or a SOAP fault response from the server should be escalated and paired with the host leads, and the rule generalizes to every application still running Axis 1.x.

Hunt Lead Level: 2 (Pro)

ATT&CK: Initial Access → T1190 (Exploit Public-Facing Application)

Sources: Huntback (above), additional source, same campaign; BleepingComputer (above), source article; “VULN-2026-0009”, Previdian, Nov. 12, 2026, https://previdian.com/VULN-2026-0009 (additional source, same campaign, cited by the source article)

nable_wrapper setLDFileOwner Followed by serverControl

The Python script the operator pipes into python3 (SHA-256 in the appendix) refuses to run as root and stops if /var/opt/n-central/flag/flag_default.json already exists. Otherwise it backs up /opt/nable/var/ncsai/scripts/ServerChild.sh to /var/opt/n-central/tmp/serverchild-<hex>.bak, creates flag_default.json as a symlink to ServerChild.sh, and runs sudo /opt/nable/usr/sbin/nable_wrapper.pl setLDFileOwner, which changes the owner of the flag file, follows the symlink and gives ServerChild.sh to nable. It then rewrites ServerChild.sh to call a stage-two script and runs sudo nable_wrapper.pl serverControl noop –wait, which executes ServerChild.sh as root; stage two restores the original file and ownership, removes the symlink and backup, runs the operator’s command and prints write_before, write_after and helper_restored for the operator. The detection logic is to alert when nable_wrapper.pl setLDFileOwner and serverControl noop –wait are invoked through sudo within a few minutes of each other by a process descended from the web application’s Java process or from python3, and on any ownership change or write to ServerChild.sh outside a vendor upgrade.

Use sudo logs (/var/log/secure or the journal), auditd rules watching execve of nable_wrapper.pl and writes or chown on /opt/nable/var/ncsai/scripts/ServerChild.sh, and file integrity monitoring on that script. Baseline normal nable_wrapper.pl usage for 30 days; scheduled maintenance will show regular callers and times. Look back to Nov. 12, 2026. Allowlist by parent process and schedule, not by the wrapper name, since the attacker uses the legitimate helper. Because the script restores the file it changed, a file hash check after the fact will look clean; the sudo and audit trail is where the evidence lives. Any pairing from the web-stack process tree should be escalated as a confirmed root compromise.

Hunt Lead Level: 2 (Pro)

ATT&CK: Privilege Escalation → T1068 (Exploitation for Privilege Escalation)

Sources: Huntback (above), additional source, same campaign; BleepingComputer (above), source article

Raw TCP Callback and CPU-Capped Miner from the nable Account

The first-stage command runs as nable, the account the N-central web stack uses, and sends its output straight back to the operator through Bash’s /dev/tcp redirection to 157.20.241[.]16 on a per-request port, while a base64-decoded Python script is fed to python3 on standard input. After escalation, the root command remounts /tmp exec and pipes curl output from the payload host into sh with the rig label as argument, and the miner then runs with –cpu-max-threads-hint 50, at most eight threads, and switches RandomX to light mode on two threads when free memory is under 2.5 GB, which keeps load low enough to avoid quick notice; the rig ID nc_<victim-ip> and –donate-level 1 appear on its command line. The correlation to build is a sequence on the N-central host: a shell or python3 process whose ancestor is the web application’s Java process, an outbound TCP connection from that tree to an external address on a high port, then within minutes a curl-to-sh pipeline, and finally a new long-running process holding a steady fraction of CPU with –rig-id, –donate-level or –cpu-max-threads-hint on its command line.

Use EDR or auditd process execution with full command lines and parent chains, NetFlow or firewall egress logs for the N-central server, and host CPU metrics from monitoring. Baseline the server’s normal child processes of the Java service and its outbound destinations over 30 days; an RMM server talks to many agents, so anchor egress on connections initiated by shells rather than on volume. Because the miner is capped at half the cores, a CPU threshold alert alone may never fire; compare against the per-host baseline instead. Hash-blocking XMRig is the wrong control because the operator can swap builds and the stock tarball is a public release. Any shell from the web stack with a /dev/tcp callback should be escalated immediately, and the pattern generalizes to the operator’s other targets, which Huntback lists as Jpom, FreePBX, MLflow, Flink, PaperCut, SFTPGo and AJ-Report.

Hunt Lead Level: 3 (Elite)

ATT&CK: Execution → T1059.004 (Command and Scripting Interpreter: Unix Shell); Impact → T1496.001 (Resource Hijacking: Compute Hijacking)

Sources: Huntback (above), additional source, same campaign; BleepingComputer (above), source article

Hash Appendix

4EverAble2Shell escalation script

The SHA-256 comes from Huntback’s write-up (additional source); the source article published no hashes, and MD5 and SHA1 were not published and have not been filled in from OTX or VirusTotal for this report. The miner fallback is stock XMRig 6.26.0, a public release; do not hash-block it, detect the command line and persistence instead.

MD5s

(not available)  # nable-to-root Python script -> piped into python3 from the SOAP payload

SHA1s

(not available)  # nable-to-root Python script -> piped into python3 from the SOAP payload

SHA256s

fc4c01fd11bc301cf312830460cfdccc3af9dcfe50c910b86d6a1117bc76c747  # nable-to-root Python script -> piped into python3 from the SOAP payload

References Appendix

  • “New N-able “4EverAble2Shell” zero-day exploited hours after PoC released”, BleepingComputer, Nov. 12, 2026, https://www.bleepingcomputer.com/news/security/new-n-able-4everable2shell-zero-day-exploited-hours-after-poc-released/ (source article; disclosure, chain, Previdian and Huntback findings)
  • “4EverAble2Shell is already mining Monero on live N-central servers”, Huntback, Nov. 12, 2026, https://huntback.io/blog/ncentral-4everable2shell-miners-on-live-servers (timeline, payload, escalation steps, indicators, victim counts)
  • “VULN-2026-0009”, Previdian, Nov. 12, 2026, https://previdian.com/VULN-2026-0009 (N-central privilege escalation tracking entry)
  • CVE-2026-90436 (Apache Axis 1.x SOAP fault class instantiation), NVD, Nov. 6, 2026, https://nvd.nist.gov/vuln/detail/CVE-2026-90436
  • MITRE ATT&CK Enterprise technique pages linked above, MITRE, https://attack.mitre.org/

CVE at a glance

CVE-2026-90436CriticalPublic exploitApache Software Foundation Apache Axis 1.x (EOL)
CVSS
9.8 Critical (v3.1)
EPSS
1.1% chance of exploitation in the next 30 days (higher than 66.8% of CVEs)
Exploited in the wild
Not on CISA’s KEV list
Public exploit
Yes, reported in 1 GitHub repository

Full CVE details

Data from NVD, FIRST EPSS and CISA KEV, refreshed automatically. We report whether public exploit code exists but never link to it: fake proof-of-concepts that infect researchers are common.

More from the Roundup