HF2 is not the close. Legacy API off is containment. 19 of 21 already had the patch.
Huntback counted 21 production N-central servers mining Monero at 12:50 UTC 12 November; 19 reported 2026.4.1.26. First probe 08:30 UTC, first root command 09:16 UTC, four and a half hours after the 03:58 UTC PoC. N-able says the server chain needs the non-default Legacy API internet-exposed. Hosted restrictions are applied. On-prem disable is the partner. A miner is not the compromise.
Bottom line up front
CONFIRMED On 12 November 2026, a public 4EverAble2Shell chain was used against internet-reachable N-able N-central servers. Huntback’s census at 12:50 UTC: 21 production servers submitting Monero shares under nc_<ip> labels; 19 reported build 2026.4.1.26 — N-central 2026.4 Hotfix 2, shipped 10 November for Able2Shell. First decoy check 08:30 UTC. First weaponized request 09:16 UTC. PoC landed in the public repository at 03:58 UTC. Same source address, 157.20.241.16, seen by Huntback and Previdian. Lupovis independently restated the 21-rig wallet and the geography. N-able has not published that count. On 13 November the vendor said it had identified additional IoCs and was working with those customers.
Do not collapse five facts.
- This is not Able2Shell, and 2026.4.1.26 is not the close. Hotfix 2 addressed seven CVEs from the 9 November disclosure: CVE-2026-125883, CVE-2026-125878, CVE-2026-125879, CVE-2026-125880, CVE-2026-125881, CVE-2026-125882, CVE-2026-91000. 4EverAble2Shell is a later chain. The researcher tested it against HF2. Huntback’s 19 patched victims are the operator sentence.
- The vendor control for the server path is Legacy API off, not another version bump. N-able: the described server issue depends on a non-default configuration — Legacy API on and exposed to the public internet. Off by default, not recommended. Hosted: N-able applied restrictions, including Legacy API off and Intune integration disabled; no server-side action for hosted. On-prem: the partner disables it. Huntress: HF2 with Legacy API disabled is not exposed to this chain. Confirm the setting. An upgrade can preserve an earlier on.
- A miner is not the incident. Huntback: XMRig is the only payload observed. The escalation still hands root on a host that manages customer endpoints. Treat a hit as full compromise of the RMM, not a cleanup of
/tmp/.xvd. Do not skip credential rotation, agent/probe review, or rebuild because the pool looks like cryptojacking. - Agent2Shell is a separate claim, not this campaign’s confirmed payload. Huntress reviewed more than ten issues in how the server talks to Windows Agents and Probes; two claimed chains let an unauthenticated attacker who can reach the server run commands on managed Windows endpoints, including as SYSTEM. Huntress has not confirmed whether those chains also require Legacy API. Huntress, as of the 12 November 06:30 ET update, had not observed exploitation in partner environments. Do not write “SYSTEM on every agent” as a Huntback fact. Do not skip the agent hunt because the miner was on the appliance.
- This is not on KEV, and it is not ScreenConnect, Barracuda, or SSHole. Live catalog this run:
2026.11.10/ 1779,dateReleased2026-11-10T19:03:29Z. No new CISA add overnight. CVE-2026-90436 (Apache Axis 1.x through 1.4, SOAP-fault class instantiation, CVSS 9.8, EOL, no 1.x release planned) is the Axis row in the chain. It is not on this catalog. The N-central helper step has no CVE in vendor notes; Previdian tracks it as VULN-2026-0009. [Yesterday’s ScreenConnect / SCKit](/posts/2026-11-12-sckit-rmmplus-screenconnect/) is a different RMM. [Barracuda ESG CVE-2026-116606 / CVE-2026-111560](/posts/2026-11-11-barracuda-esg-kev/) and Ivanti CVE-2026-118527 are due today, 13 November, forensic triage Yes. [SSHole four-pack](/posts/2026-11-10-sshole-four-kev/) was due yesterday.
The operator sentence: if you run on-prem N-central, the floor today is confirm Legacy API is off, hunt /dms/services/ServerUI SOAP faults and miner artefacts from 11 November onward, and treat HF2 as last Tuesday’s Able2Shell ticket, not this one. 21 is Huntback’s miner census. It is not N-able’s victim list. Neither is a green row.
What happened
12 November 2026, after yesterday’s 06:00 ET Daily Top. Independent researcher Sean Bales added 4EverAble2Shell and Agent2Shell to a public repository at 03:58 UTC, two days after N-able shipped HF2 for the 9 November Able2Shell drop (33 claimed findings, hosted taken offline, then restored on 2026.4.1.26). A repository update at 07:48 UTC covered the Legacy API requirement. Huntback’s decoy saw POST /dms/services/ServerUI checks from 157.20.241.16 at 08:30 UTC (user-agent Mozilla/5.0), then weaponized requests from 09:16 UTC (user-agent python-requests/2.31.0). Previdian reported the same IP and the same Java class against its honeypot. At 12:50 UTC Huntback read a public mining-pool account: 21 rigs named nc_<victim-ip>, all with a share in the previous five minutes. HTTPS checks: all 21 served N-central; 19 advertised 2026.4.1.26; geography United States (9), South Africa (4), Canada (4), United Kingdom, Germany, France, Sweden (1 each). Three sat in one MSP address block. Huntback: decoy labels are not on the pool — every nc_ rig is a real server that ran the chain to the end.
N-able’s sequence, as published. 12 November: restrict certain features and integrations; hosted protections applied (Legacy API off by default, Intune integration turned off as a precaution); on-prem customers told to ensure Legacy API is disabled; keep upgrading Agents and Probes under the HF2 note (Agents first). N-able is not telling customers to take N-central offline this time — that was 9 November. BleepingComputer quoted a 12 November vendor line of no signs of compromise using the new flaws. 13 November: SecurityWeek quotes N-able on incident 202613 — additional IoCs identified, working with those specific customers. Do not freeze the 12 November negative as the live vendor sentence.
The on-host chain, high-level and defensive, not a reproduction. Public reporting and Huntback’s write-up agree on the shape: an unauthenticated SOAP request to the bundled Apache Axis 1.x endpoint (/dms/services/ServerUI) uses CVE-2026-90436 so a classpath class is instantiated before service authentication handlers run. Command execution is as nable. A separate N-central maintenance-helper weakness then yields root. The observed root command fetched jup.sh from 157.20.241.16:8080 and installed XMRig (half the cores, at most eight threads; systemd xvd.service or cron persistence). Huntback: the same wallet already mined other internet products (Jpom, FreePBX, MLflow, Flink, PaperCut, and others). Treat that as an opportunistic miner operator picking up a new public exploit in hours — not a named APT, not a ransomware overlay.
Apache Axis is EOL. oss-security, 6 November: Axis 1.x through 1.4, UNSUPPORTED WHEN ASSIGNED. The project does not expect a 1.x release. Documented options are migrate to Axis 2 or apply commit 41f3b4e8. N-central’s SOAP stack is the product that still exposes it. Disabling Legacy API is N-able’s stated containment for this server path; it is not an Axis 1.x patch for every other product that still ships 1.4.
Not this increment as a reprint. CISA KEV freeze is still 2026.11.10 / 1779. CISA ICS did move on 12 November: ICSA-26-316-01 through -05 (Siemens Building Automation / Energy including PHP2Shell CVE-2026-109618 / 109619 in Spectrum Power and related products; Desigo / Gridscale; Industrial Edge Management; two RUGGEDCOM APE1808 notes, one restating Brotli CVE-2026-111497 / PAN-OS Node2Shell). Those are vendor-ICS rows, not confirmed exploitation of N-central, and not a process-impact claim. GitHub wfx-loot (Aikido: 4,837 hijacked accounts, probe PRs across ~61,764 repositories, secrets stolen from at least ~1,800) started 10 November 12:45 UTC and was still being counted on 12 November. Real CI-secret incident. It is not root on an MSP console.
Why it matters
Three operational reasons this is the daily.
First: the false close is the HF2 ticket. Able2Shell was the 9–10 November stop-all. HF2 restored hosted and gave on-prem a build number. 4EverAble2Shell is the next day’s public chain against that build when Legacy API is on. Nineteen of Huntback’s twenty-one already had the patch. An MSP that closed “we are on 2026.4.1.26” on Wednesday and skipped the Legacy API check on Thursday is the victim shape.
Second: the blast radius is the RMM, not 21 miners. Each N-central server is a management plane for customer endpoints. Huntback’s payload was XMRig. The access is root. Agent2Shell, if it works as Huntress summarized the published code, is a path from that server to Windows Agents and Probes as SYSTEM. Huntress has not confirmed that hop in the wild. The defensive posture is still: assume the console can talk to the estate, hunt both, rebuild a hit.
Third: today’s KEV clocks are still live and they are not substitutes. Barracuda ESG 116606 / 111560 and Ivanti Connect Secure 118527 are due today with forensic triage Yes. An MSP that spends Friday only on N-central and misses an ESG restore hunt, or tickets N-central as the Barracuda close, has sequenced the wrong asset. ScreenConnect SCKit from yesterday is a different panel.
This is not confirmed OT or ICS process impact. An MSP whose customers include a water utility, a hospital, or a plant is still an IT/RMM compromise of the management server until someone shows the same host writing a controller. Siemens’s 12 November ICS notes are a parallel patch queue, not this incident.
Who / what is affected
| Asset | What the sources say | Floor / action | Who should care first |
|---|---|---|---|
| On-prem N-central, Legacy API on and internet-exposed | N-able: this is the server-issue precondition; researcher tested HF2 | Disable Legacy API now via N-able’s KB; hunt from 11 Nov; treat as potentially compromised | On-prem partners — this is the gap |
| On-prem N-central, Legacy API off | Huntress: HF2 + Legacy API disabled is not exposed to this chain | Confirm the setting survived upgrade/automation; still hunt SOAP faults if it was ever on | Anyone who “knows it’s default off” |
| Hosted N-central (NCOD) | N-able: hosted not affected by this server issue; restrictions applied | No server-side action; still upgrade Agents/Probes; watch status | Hosted MSPs |
| N-central 2026.4.1.26 (HF2) | Closes Able2Shell’s seven CVEs; not 4EverAble2Shell | Keep it; do not treat it as today’s close | Anyone who closed Able2Shell on this build |
| Agents and Probes | HF2 changes Agent–Probe communication; Agents first | Upgrade both; Huntress: Agent2Shell still unconfirmed in the wild and unconfirmed vs Legacy API | Every customer of an affected server |
| Windows endpoints behind a hit server | Designed Agent2Shell SYSTEM path; miner campaign has not shown it | Hunt N-able Agent/Probe children, unexpected probe restarts, from a clean channel | Service desks; do not use the suspect N-central to triage |
| Apache Axis 1.x through 1.4 elsewhere | CVE-2026-90436, EOL, no 1.x release | Inventory SOAP endpoints; not this RMM ticket | Teams that still ship Axis 1.4 |
| Not this row | ScreenConnect SCKit; Barracuda ESG due today; SSHole due yesterday | Follow those vendors | Separate queues |
No public internet-census of Legacy-API-exposed N-central is in these sources. Treat exposure as an inventory problem.
Technical context
High-level, defensive only. Not a reproduction.
The observed access path is an unauthenticated request to N-central’s Axis SOAP endpoint that CVE-2026-90436 turns into code execution as nable, then a local helper to root, then a miner installer. Huntback and Huntress both name detection on POST /dms/services/ServerUI whose body is a SOAP fault with exceptionName jline.internal.TerminalLineSettings. Weaponized requests in this campaign used user-agent python-requests/2.31.0; the earlier checks used Mozilla/5.0. Hashes of on-the-fly scripts will rotate; Huntback published SHA-256 fc4c01fd11bc301cf312830460cfdccc3af9dcfe50c910b86d6a1117bc76c747 for the nable-to-root Python it recovered — supplementary, not a close.
ATT&CK mapping for defender queries, not a playbook: T1190 Exploit Public-Facing Application (Axis SOAP on N-central), T1068 Exploitation for Privilege Escalation (nable → root helper), T1105 Ingress Tool Transfer (jup.sh / XMRig), T1496 Resource Hijacking (Monero), T1053.005 Scheduled Task / cron (xvd.service, # xvkeep, /etc/cron.d/xvd), T1072 Software Deployment Tools (N-central as the estate manager — capability, Agent2Shell not observed in this miner wave).
Public 4EverAble2Shell / Agent2Shell repositories, WatchTowr-style generators, and Axis SOAP samples are untrusted input. They are not required to contain. Inventory, disable Legacy API, hunt, rebuild a hit. Do not replay them.
Threat / exploitation status
| Claim | Status | Confidence |
|---|---|---|
| Public 4EverAble2Shell PoC 03:58 UTC 12 Nov; Legacy API note 07:48 UTC | CONFIRMED (repository timing via Huntback) | High |
| Probes from 157.20.241.16 at 08:30 UTC; weaponized at 09:16 UTC | CONFIRMED (Huntback + Previdian) | High |
21 production N-central servers mining as nc_<ip> at 12:50 UTC; 19 on 2026.4.1.26 | CONFIRMED as Huntback/Lupovis telemetry | High for that census; UNKNOWN for industry-wide total; N-able has not published 21 |
| Payload observed: XMRig via jup.sh | CONFIRMED (Huntback) | High for those 21 |
| N-able: server issue needs Legacy API on + internet-exposed; hosted not affected | CONFIRMED as vendor statement | High for the statement |
| HF2 with Legacy API disabled not exposed to this chain | CONFIRMED as Huntress restatement of vendor + researcher repo update | High for this chain; not a blanket for Agent2Shell |
| N-able 13 Nov: additional IoCs, working with specific customers | CONFIRMED as vendor statement | High for the statement; scope UNKNOWN |
| Agent2Shell SYSTEM on Windows agents in this campaign | NOT OBSERVED | — |
| Agent2Shell requires Legacy API | UNKNOWN (Huntress: not yet confirmed) | — |
| Named actor / ransomware overlay | UNKNOWN | — |
| CVE for the N-central helper / KEV add | None as of catalog 2026.11.10 / 1779; Axis is CVE-2026-90436, not on KEV | High |
| Same incident as Able2Shell’s seven CVEs, ScreenConnect SCKit, or Barracuda | No evidence | High they are separate |
| OT/ICS process impact | UNKNOWN / not claimed | — |
What defenders should do
- Inventory the setting before you trust the build. On-prem vs hosted. Actual Legacy API state on the appliance, not the default in the datasheet. Build number (2026.4.1.26 is Able2Shell’s floor, not 4EverAble2Shell’s). Whether Legacy API was ever on and reachable from 11 November. Agent and Probe versions relative to HF2 (Agents first). Do not use the suspect N-central to triage itself.
- Contain the server path, then hunt. On-prem: disable Legacy API using N-able’s article. If you believe you still need it, Huntress: do not expose it to the internet; restrict access until N-able ships a fix. Hosted: N-able says it already applied the restriction. Intune integration is off as a vendor precaution — do not treat that as a hunt skip. N-able is not ordering another take-down.
- Hunt the artefacts Huntback, Huntress, and Previdian named, then assume they will change. SOAP POSTs to
/dms/services/ServerUIwithjline.internal.TerminalLineSettings. Huntress also listed/dms/services/ServerUIwithGenericAgentXMPPMessageExchangeSessionID-1, and/dms2/services2/ServerMMS2RemoteExecutionTaskSubmitsessionID-1(from static review of the published code; not claimed as this miner’s telemetry). Files:/tmp/.xvd/or/var/tmp/.xvd/;serverchild-*.bak/.sh/.outunder/var/opt/n-central/tmp/; symlink at/var/opt/n-central/flag/flag_default.json. Persistence:xvd.service,/etc/cron.d/xvd, crontab# xvkeep. Process:--rig-id nc_or binaryxfrom.xvd. Network: 157.20.241.16 (8080 and TCP 19202–19418), 139.99.69.109:10128, 79.76.51.56:39100. Unexpected administrator accounts, scripts, scheduled tasks, remote sessions from 11 November.
- A hit is a rebuild, not a miner uninstall. Huntback’s sentence stands: full compromise of a host that manages customer endpoints. Preserve logs and disk. Rebuild from a known-good image. Rotate every credential the server stored — N-central passwords, API keys, stored SNMP/community strings, remote-control secrets, IdP/app registrations, Agent/Probe enrollment material. Review managed endpoints from a clean channel (EDR live response, not the suspect console). Huntress’s Agent2Shell host clues (encoded PowerShell as SYSTEM from the N-able Agent; unexpected
wsp.exe/service.cfgunder Windows Software Probe; probe service stop/start from%TEMP%) are code-derived, not observed in the miner wave — still worth querying if the server was exposed.
- Keep the other clocks. [Barracuda 116606/111560](/posts/2026-11-11-barracuda-esg-kev/) and Ivanti CVE-2026-118527: federal due today, forensic triage Yes. [SSHole four-pack](/posts/2026-11-10-sshole-four-kev/) was due yesterday — a package without an
sshdrestart is still open. [ScreenConnect SCKit](/posts/2026-11-12-sckit-rmmplus-screenconnect/): five extensions stay disabled; TrapWatch is still an endpoint hunt. Siemens 12 November ICS (PHP2Shell in Spectrum Power / Energy Engage; Brotli on RUGGEDCOM APE1808) is a parallel OT patch queue, not this RMM. Do not publish or replay 4EverAble2Shell, Agent2Shell, or Axis SOAP payloads.
RWP assessment
Score 9.4. It outranks GitHub wfx-loot (Aikido-scale CI-secret theft from 10–12 November; 4,837 accounts / ~61k probe PRs / ≥1,800 confirmed runs — real, but not an MSP root shell), CISA’s 12 November ICS batch (Siemens PHP2Shell product mapping and RUGGEDCOM Brotli/PAN-OS notes — vendor ICS, not confirmed exploitation), [yesterday’s ScreenConnect / SCKit](/posts/2026-11-12-sckit-rmmplus-screenconnect/) (no material overnight increment in the sources we opened), and today’s Barracuda / Ivanti due rows (already Daily Tops; clock only).
The material development is not “N-able had a bad week.” Able2Shell was a 9 November disclosure with a vendor stop-all and, at hotfix time, no confirmed customer compromise. Overnight the story became a new chain, tested on HF2, exploited in hours, with a Huntback victim census that is mostly already patched, and a 13 November vendor IoC sentence. Legacy API off is containment for the server path. It is not a hunt, not an Agent2Shell close, and not a KEV row. We will not invent a CVE for the helper, an actor, ransomware use, SYSTEM-on-agents in this wave, or OT process impact.
What we are watching
- Whether N-able or a CNA assigns a CVE to the helper step, or CISA puts CVE-2026-90436 / the N-central chain on KEV.
- Whether N-able publishes a follow-up hotfix that removes the Axis path even with Legacy API on, or revises hosted/on-prem scope.
- Whether Huntress, Previdian, or N-able confirms Agent2Shell in the wild, or confirms it does not need Legacy API.
- Growth past Huntback’s 21, or payloads other than XMRig (ransomware, data theft, mass Agent tasking).
- Relationship, if any, between N-able’s 13 November customer IoCs and the 157.20.241.16 miner wave.
- Barracuda Friday forensic-triage closeouts that hunt restored configs, not only firmware; Ivanti 118527 the same clock.
- Siemens ICSA-26-316-01 products still on PHP2Shell without a fix (AMIS TS, Energy Engage V2.0SP9, several Spectrum Power 4 roles).
- wfx-loot persistence after secret rotation (federated credentials named
wfx-ci-, AWS trust"Principal": {"AWS": ""}).
Sources
- Huntback — 4EverAble2Shell exploited: Monero miners on live N-central, 12 Nov 2026
- Huntress — N-able disables cloud services following Able2Shell disclosure (updates through 12 Nov 2026 06:30 ET)
- BleepingComputer — New N-able 4EverAble2Shell zero-day exploited hours after PoC released, 12 Nov 2026
- The Hacker News — Hackers Exploit N-central Flaws to Infect 21 Servers, Including 19 Running Hotfix 2, 13 Nov 2026
- SecurityWeek — Hackers Exploit New N-central Zero-Day Hours After PoC Publication, 13 Nov 2026
- N-able — N-central 2026.4 HF2 Release Notes, build 2026.4.1.26, 10 Nov 2026
- N-able — Status incident 202613, November 12 update / 13 Nov IoC note
- N-able — How to Disable Legacy API settings on On-Premises N-central servers
- N-able — How to upgrade Agents and Probes on N-central 2026.4 HF1 and above
- Previdian — VULN-2026-0009 N-central 4EverAble2Shell
- Apache Software Foundation / oss-security — CVE-2026-90436 Apache Axis 1.x SOAP fault class instantiation, 6 Nov 2026
- CISA — Known Exploited Vulnerabilities Catalog
- CISA — KEV JSON feed catalog 2026.11.10
- CISA — ICS Advisories, 12 Nov 2026 (ICSA-26-316-01 through -05)
- CISA — Siemens Building Automation and Energy Products, ICSA-26-316-01
- CISA — Siemens RUGGEDCOM APE1808, ICSA-26-316-04
- BleepingComputer — Hackers compromise 4,800 GitHub accounts to steal cloud credentials (wfx-loot), 12 Nov 2026
- RWP Ventures — ScreenConnect SCKit / RMM+ Daily Top 2026-11-12
- RWP Ventures — Barracuda ESG KEV Daily Top 2026-11-11
- RWP Ventures — SSHole four-pack KEV Daily Top 2026-11-10
- RWP Ventures — PHP2Shell Daily Top 2026-10-22
- RWP Ventures — Brotli KEV Daily Top 2026-10-28