4EverAble2Shell Exploited on 21 N-central Servers, Report Says

Summary
4EverAble2Shell reportedly gives unauthenticated root access to internet-exposed N-able N-central servers with the Legacy API enabled. Huntback telemetry identified 21 servers mining Monero; no fix is available, and N-able advises disabling the API.
Key points
- The two-stage chain uses a crafted SOAP fault against bundled Apache Axis to gain command execution as the nable service account, then exploits an N-central helper-script weakness to escalate to root.
- The server chain requires an on-premises N-central server with the Legacy API enabled and reachable from the internet; N-able says hosted N-central is not affected.
- Huntback telemetry reportedly recorded the first weaponized request on November 12, 2026, and its analysis identified 21 mining rigs; the observed payload was XMRig.
- Nineteen of the 21 identified servers were running N-central 2026.4 Hotfix 2, which does not stop the chain.
- No fix is available for the chain. N-able’s main recommended control is disabling the Legacy API; if that cannot be done immediately, the article advises removing internet exposure and using a VPN or trusted management network.
- For systems matching the indicators, the article recommends isolation, evidence preservation, rebuilding from a known-good installation, and rotating credentials stored in or used by N-central.
- The separate Agent2Shell exploit set reportedly enables SYSTEM-level command execution on managed Windows endpoints; no exploitation of it has been reported.
Article Details
- Vulnerability Types
- Remote command execution
- Local privilege escalation
- Severity
- CVSS 9.8 (CVSS v3.1, CISA ADP) for CVE-2026-90436; no official score for the full exploit chain
- Affected Versions
- N-able N-central 2026.4 Hotfix 2 (build 2026.4.1.26)
- N-able N-central build 2025.3.1.9
- Exploitation Status
- active
- Exploit Availability
- public_poc
- Patch Status
- unavailable
- Workarounds
- Disable the Legacy API on on-premises servers.
- As a short-term measure, remove the server from the internet or put its web and SOAP endpoints behind a VPN or trusted management network.
Indicators of compromise
| Type | Indicator | Context |
|---|---|---|
| IPV4 | 139[.]99[.]69[.]109 | Network indicator published by researchers from the observed attacks. |
| IPV4 | 157[.]20[.]241[.]16 | Network indicator published by researchers from the observed attacks. |
| IPV4 | 79[.]76[.]51[.]56 | Network indicator published by researchers from the observed attacks. |
| SHA256 | fc4c01fd11bc301cf312830460cfdccc3af9dcfe50c910b86d6a1117bc76c747 | SHA-256 hash of the privilege-escalation script identified in the attack indicators. |
MITRE ATT&CK
T1053.003 · CronThe miner is configured to persist through cron.T1059.004 · Unix ShellAttackers use a downloaded shell script to install the miner.T1068 · Exploitation for Privilege EscalationA weakness in an N-central helper script escalates access from the nable service account to root.T1105 · Ingress Tool TransferAttackers download a shell script and the XMRig miner to compromised servers.T1190 · Exploit Public-Facing ApplicationThe exploit chain targets internet-facing N-central servers through the Legacy API and a crafted SOAP fault.T1496 · Resource HijackingAttackers install a Monero miner on compromised N-central servers.T1543.002 · Systemd ServiceThe miner is configured to persist through a systemd service.
CVE
People
Malware
Vendors
Products
Countries
CanadaBy 12:50 UTC, the operator’s mining pool listed 21 rigs named after N-central servers, located in the United States, South Africa, Canada, the UK, Germany, France and Sweden.FranceBy 12:50 UTC, the operator’s mining pool listed 21 rigs named after N-central servers, located in the United States, South Africa, Canada, the UK, Germany, France and Sweden.GermanyBy 12:50 UTC, the operator’s mining pool listed 21 rigs named after N-central servers, located in the United States, South Africa, Canada, the UK, Germany, France and Sweden.South AfricaBy 12:50 UTC, the operator’s mining pool listed 21 rigs named after N-central servers, located in the United States, South Africa, Canada, the UK, Germany, France and Sweden.SwedenBy 12:50 UTC, the operator’s mining pool listed 21 rigs named after N-central servers, located in the United States, South Africa, Canada, the UK, Germany, France and Sweden.United KingdomBy 12:50 UTC, the operator’s mining pool listed 21 rigs named after N-central servers, located in the United States, South Africa, Canada, the UK, Germany, France and Sweden.United StatesBy 12:50 UTC, the operator’s mining pool listed 21 rigs named after N-central servers, located in the United States, South Africa, Canada, the UK, Germany, France and Sweden.
