SecOraLens
CriticalAPT

4EverAble2Shell At a Glance

SOCRadar·Source published ·1 min read

What happened?

4EverAble2Shell is an N-central zero-day exploit chain that lets an unauthenticated remote attacker run commands as root on an on-premises N-able N-central server. An independent researcher released a proof of concept (PoC) early on November 12, 2026, and attackers used it to install cryptocurrency miners on at least 21 servers within hours. The chain works against fully patched servers when the Legacy API is turned on and reachable from the internet. N-able is restricting some N-central features while it develops further remediation.

Key details

  • 4EverAble2Shell is an unauthenticated remote exploit chain giving root on on-premises N-central servers with Legacy API enabled and internet-facing.
  • The chain works against fully patched servers including those running Hotfix 2; 19 of 21 compromised servers were on Hotfix 2.
  • First stage uses CVE-2026-90436 in Apache Axis 1.x to run commands as the nable service account via a crafted SOAP fault.
  • Second stage escalates from nable account to root through a weakness in an N-central helper script.
  • Attackers exploited the chain within hours of the public PoC on November 12, 2026, installing XMRig Monero miners on at least 21 servers.
  • Hosted N-central is not affected by the server chain; Legacy API is off by default and N-able disabled Intune integration as a precaution.
  • Agent2Shell companion exploit targets managed Windows endpoints for SYSTEM-level execution but no exploitation has been reported.

What is affected?

  • On-premises N-able N-central with Legacy API enabled and internet-facing.
  • Confirmed on builds 2025.3.1.9 and 2026.4 Hotfix 2 (2026.4.1.26); full version range not published.

How do I fix or mitigate it?

  1. If indicators match, treat server as fully compromised: isolate, preserve evidence, rebuild from known-good installation, rotate all N-central credentials.

What should defenders look for?

  • Network: 157.20.241[.]16 (ports 8080, 19202-19418), 139.99.69[.]109:10128, 79.76.51[.]56:39100.
  • Web requests: POSTs to /dms/services/ServerUI with SOAP fault containing exceptionName field; user agent python-requests/2.31.0.
  • Files: /tmp/.xvd or /var/tmp/.xvd; serverchild-* in /var/opt/n-central/tmp/; /var/opt/n-central/flag/flag_default.json as symlink.
  • Persistence: /etc/systemd/system/xvd.service; /etc/cron.d/xvd; crontab line ending in # xvkeep.
  • Process: command lines containing --rig-id nc_ or --donate-level 1.
  • SHA-256: fc4c01fd11bc301cf312830460cfdccc3af9dcfe50c910b86d6a1117bc76c747 (privilege escalation script).

Summarised by SecOraLens from SOCRadar. Always read the original source before acting. How SecOraLens verifies advisories.

What to do next

For CISOs and SOC leads

Brief your board. Brief your team.

Executive risk briefs for governance, technical kill-chains for the SOC — delivered as advisories publish. Critical alerts within 1 hour. No spam, unsubscribe anytime.