Exploitation / MSP RMMHighTLP:CLEAR

Able2Shell N-central

Able2Shell N-able N-central Zero-Days

Published
9 November 2026
Added
12 November 2026, 09:55 UK
Last updated
14 November 2026

8 to block now12 to hunt10 behaviours to hunt

Hunt3 platforms

Run the hunt before you block, to find past activity. The same hunt is published for each platform. Preview and copy the queries in the dashboard.

  • Defender XDRKQLDefender portal > Hunting > Advanced hunting. Paste and run over 30 days.Download hunt.kql
  • SplunkSPLSearch & Reporting, last 30 days or more. Reads the CIM data models.Download hunt.spl
  • Google SecOpsYARA-L 2.0Rules Editor. Paste, Retrohunt over 30 days, then turn on live mode.Download hunt.yaral

These queries can return false positives. Know your environment and confirm a hit before acting.

Summary

4EverAble2Shell is installing XMRig on live N-central servers, including hosts already on HF2; block 157[.]20[.]241[.]16 and hunt xvd artefacts. Applying HF2 is not enough: keep the Legacy API disabled and follow N-able's current guidance.

Do now

  1. Block the 8 indicators.
  2. Run the hunt.
  3. Check for flag_default.json.

Indicators 20

ValueTypeActionCopy
5[.]231[.]45[.]175IPv4block
157[.]20[.]241[.]16IPv4block
hxxp://157[.]20[.…080/jup.shURLblock
hxxp://157[.]20[.…:8080/xvgzURLblock
hxxp://157[.]20[.…/xmrig.tgzURLblock
hxxp://157[.]20[.…ob/cronhitURLblock
hxxp://157[.]20[.…/ob/fcheckURLblock
fc4c01fd11bc301cf…17bc76c747SHA256block
3[.]74[.]48[.]121IPv4alert
hxxp://5[.]231[.]…8097/a.dtdURLalert
hxxp://5[.]231[.]…97/svc.xmlURLalert
139[.]99[.]69[.]109IPv4alert
79[.]76[.]51[.]56IPv4alert
41wx2Pv3FzfRvX11j…NXoB19mGtrOtheralert
jline[.]internal[…neSettingsOtheralert
/tmp/.xvdFile namealert
/var/tmp/.xvdFile namealert
/etc/systemd/syst…vd.serviceFile namealert
/etc/cron.d/xvdFile namealert
# xvkeepOtheralert

Sources Huntress · Beazley Security · Previdian · N-able · Tenable · Rapid7 · The Hacker News · X · huntback.io · BleepingComputer · N-able (2)

More detail
Note huntback confirmed 21 live N-central servers mining on 12 November but did not publish their addresses, including one in the United Kingdom. 139[.]99[.]69[.]109 and 79[.]76[.]51[.]56 are mining-pool endpoints used by this operator; alert on them, do not block the whole addresses without reviewing impact. Huntress's Agent2Shell file and process indicators come from static analysis of the public code and may not match modified exploits. 3[.]74[.]48[.]121 is AWS: alert only.

What to do

  1. Take on-premises N-central servers off the internet, even on 2026.4 HF2, until N-able publishes a fix for 4EverAble2Shell and Agent2Shell; do not rely on IP allowlisting alone, because agents and probes use the same endpoints.
  2. Block 5[.]231[.]45[.]175 and 157[.]20[.]241[.]16, and the installer URLs on hxxp://157[.]20[.]241[.]16:8080/, at the perimeter; alert on 3[.]74[.]48[.]121 and on the mining-pool addresses 139[.]99[.]69[.]109 and 79[.]76[.]51[.]56, and search N-central web and proxy logs from 8 November for these addresses, for jline[.]internal[.]TerminalLineSettings in /dms/services/ServerUI requests, and for /tmp/.xvd, xvd.service and --rig-id nc_ miners.
  3. On the server, look for new or enabled Default Administrator accounts, unexpected password resets, new scripts, software or policy deployments and remote sessions, plus serverchild-* files under /var/opt/n-central/tmp and CodeDropMeta.xml ZIPs.
  4. On managed Windows endpoints, hunt for encoded PowerShell run as SYSTEM by the N-able Agent, wsp.exe or service.cfg written to the Windows Software Probe folder, and taskkill of wsp.exe from a .cmd in %TEMP%. If anything is confirmed, treat every network managed by that server as in scope.

Behaviours to hunt 10

Behaviours are leads, not confirmed indicators, and can match legitimate activity. Compare any hit against your own baseline and environment before acting.

  1. alert N-central ServerUI or ServerMMS2 exploit requests

    Look forUnauthenticated SOAP POSTs to /dms/services/ServerUI or /dms2/services2/ServerMMS2 from external addresses, carrying SessionHello, GenericAgentXMPPMessageExchange or RemoteExecutionTaskSubmit with SessionID -1, importServiceFromFile with a remote FilePath, or an XML DOCTYPE

    Why it mattersThese are the endpoints and messages used by the public Able2Shell chains. watchTowr saw SessionHello posts to ServerMMS2, Previdian captured XXE DOCTYPE and importServiceFromFile requests to ServerUI, and Huntress lists the jline[.]internal[.]TerminalLineSettings, GenericAgentXMPPMessageExchange and RemoteExecutionTaskSubmit patterns. Agents and probes also use these endpoints, so focus on unexpected external sources and the listed message contents. Huntress

    Log sourceN-central web server, reverse-proxy and WAF logs

    QueriesSPL · YARA-L

  2. alert N-central-sec-audit/1.0 user agent

    Look forHTTP requests whose User-Agent ends in N-central-sec-audit/1.0

    Why it matterswatchTowr's published exploitation attempt used this User-Agent. It is trivial to change, so its absence does not rule out exploitation. Beazley Security

    Log sourceN-central web server, reverse-proxy and WAF logs

    QueriesSPL · YARA-L

  3. alert serverchild, flag_default.json or CodeDropMeta.xml on the server

    Look forFiles on the N-central server: /var/opt/n-central/flag/flag_default.json as a symlink to ServerChild.sh, /var/opt/n-central/tmp/serverchild-<12 hex>.bak, .sh or .out, or ZIPs under /download/scheduled_tasks/output_files/ containing CodeDropMeta.xml

    Why it mattersHuntress identified these files from static analysis of the 4EverAble2Shell and Agent2Shell code; they would appear if the public exploit is run unmodified. Huntress

    Log sourceFile integrity or EDR file events on the N-central appliance

    QueriesKQL · SPL · YARA-L

  4. hunt Encoded PowerShell as SYSTEM from the N-able Agent

    Look forpowershell.exe -NoProfile -NonInteractive -EncodedCommand run as SYSTEM by the N-able Agent or Windows Software Probe on a managed Windows endpoint

    Why it mattersAgent2Shell lets an unauthenticated attacker who can reach the server run commands on managed endpoints as SYSTEM. PowerShell is a very common child of the N-able Agent, so the encoded command line, not the process tree, is the signal; decode it and compare with scripts your MSP actually deploys. Huntress

    Log sourceEDR process events on Windows endpoints managed by N-central

    QueriesKQL · SPL

  5. alert Windows Software Probe binary or config replaced

    Look forwsp.exe or service.cfg written to the Windows Software Probe bin folder, a CodeDrop ServiceBackup copy of wsp.exe, or files in Temp CodeDropTmp

    Why it mattersHuntress lists these writes as artefacts of the Agent2Shell probe-replacement chain. The probe is normally updated by N-able, so check for writes outside a planned upgrade. Huntress

    Log sourceEDR file events on N-central probe hosts

    QueriesKQL · SPL · YARA-L

  6. alert Probe service killed from a temp .cmd

    Look fortaskkill /f /im wsp.exe or a stop and start of the Windows Software Probe Service, run from a .cmd file in %TEMP%

    Why it mattersHuntress lists this service restart from a temporary batch file as part of the Agent2Shell chain. Legitimate upgrades also restart the probe, so look at the launching script location. Huntress

    Log sourceEDR process events on N-central probe hosts

    QueriesKQL · SPL · YARA-L

  7. hunt New N-central admins, resets, scripts or sessions

    Look forNew or newly enabled N-central administrator accounts (including Default Administrator), unexpected password resets, new scripts, software or policy deployments, and remote control sessions from unfamiliar addresses since 8 November

    Why it mattersThe unauthenticated XXE chain resets an account password and can create an enabled administrator; earlier N-central exploitation was followed by scripts sprayed into managed environments. Beazley and Huntress both recommend this review. Beazley Security

    Log sourceN-central audit and login logs

    QueriesNone yet: check by hand

  8. alert Apache Axis CVE-2026-90436 or 4EverAble2Shell probe

    Look forApache Axis CVE-2026-90436 or 4EverAble2Shell probe, then root, then curl of jup.sh from 157[.]20[.]241[.]16 and an XMRig miner under /tmp/.xvd

    Why it mattersPrevidian first reported 157[.]20[.]241[.]16 attempting this chain. On 12 November huntback saw the same address weaponise 4EverAble2Shell against live N-central servers, curling hxxp://157[.]20[.]241[.]16:8080/jup.sh to install XMRig and report 21 nc_ rigs on a public pool by 12:50 UTC, 19 of them already on 2026.4 HF2. The Hacker News

    Log sourceN-central web, process and proxy logs

    QueriesKQL

  9. alert POST /dms/services/ServerUI with a SOAP fault whose exceptionName is...

    Look forPOST /dms/services/ServerUI with a SOAP fault whose exceptionName is jline[.]internal[.]TerminalLineSettings

    Why it mattersThis is the 4EverAble2Shell check and exploit. A vulnerable Axis stack instantiates the class and runs a shell command from the data field. huntback saw the word probe used for checks and a base64 Python root chain in weaponised requests, with user-agent python-requests/2.31.0. huntback.io

    Log sourceN-central web or reverse-proxy logs

    QueriesNone yet: check by hand

  10. alert After a 4EverAble2Shell hit

    Look forAfter a 4EverAble2Shell hit, files under /tmp/.xvd or /var/tmp/.xvd, a systemd unit xvd.service or cron tagged # xvkeep, and a process with --rig-id nc_ or a binary named x running from .xvd

    Why it mattersjup.sh installs XMRig this way, using half the CPU cores to stay quiet, and persists with keep.sh. Treat a hit as a full root compromise of a server that manages customer endpoints, not just a miner cleanup. Do not block the public mining-pool addresses without reviewing impact. huntback.io

    Log sourceN-central host filesystem, systemd, crontab, process and outbound network logs

    QueriesNone yet: check by hand

Affected countries and sectors

Targets
Global
Sectors
Managed service providers, IT operations

Background

An independent researcher published proof-of-concept code for 33 flaws in N-able N-central, the remote monitoring and management platform used by MSPs and IT teams, under the name Able2Shell. N-able took Hosted N-central offline on 9 November and shipped 2026.4 HF2 on 10 November, but late on 11 November the researcher released two more chains, 4EverAble2Shell (unauthenticated root RCE on the server) and Agent2Shell (commands as SYSTEM on managed Windows endpoints), which Huntress says work against HF2, so a fully patched server should be treated as vulnerable. On 12 November, about four and a half hours after 4EverAble2Shell was published, huntback Research saw 157[.]20[.]241[.]16 probe its decoys and then run the full chain, installing an XMRig miner via jup.sh. By 12:50 UTC that operator's public mining pool listed 21 production N-central servers as nc_ rigs, all submitting shares; 19 of them reported build 2026.4.1.26 (HF2). The servers were in the United States, South Africa, Canada, the United Kingdom, Germany, France and Sweden; huntback has not published the addresses. On 13 November N-able's own advisory update listed 157[.]20[.]241[.]16, its installer URLs and the two mining endpoints as indicators of compromise for servers with the Legacy API enabled. Applying HF2 is not enough: keep the Legacy API disabled and follow N-able's current guidance. Earlier N-central zero-days were exploited and are in CISA KEV, and Beazley notes past state-sponsored targeting. 5[.]231[.]45[.]175 remains a block candidate for earlier Able2Shell probing reported by Previdian and Lupovis; 157[.]20[.]241[.]16 is the live exploitation and payload host and is on the block list, along with its installer URLs and the nable-to-root script hash; the mining-pool addresses are alert only because they are public pool endpoints; the AWS address 3[.]74[.]48[.]121 is alert-only. Hunt N-central web logs for SOAP faults naming jline[.]internal[.]TerminalLineSettings, and the appliance for /tmp/.xvd, xvd.service and --rig-id nc_ miners, as well as N-able Agent child processes on managed endpoints.

Downloads

View folder in repository

MITRE ATT&CK8

Open in the live dashboard Get the blocklist