thethreatdeskFiled from the front lines of cybersecurity
VulnerabilitiesCritical

Attackers exploit N-central flaws to plant cryptominers, even on patched servers

Researchers found Monero miners on 21 N-able N-central servers within hours of exploit code going public. Nineteen were already running the latest hotfix.

Attackers began exploiting newly disclosed flaws in N-able's N-central remote management platform within hours of proof-of-concept code being published, according to SecurityWeek and The Hacker News. The flaws were among a batch disclosed by independent researcher Sean Bales.

What happened

Security firm Huntback found the XMRig Monero miner on 21 N-central servers, and 19 of them were already running Hotfix 2. The miner was set to use only half of the CPU cores, likely to avoid notice. Previdian also reported the attacks, and N-able later confirmed the targeting and shared indicators of compromise.

One chain, dubbed 4EverAble2Shell, combines a critical Apache Axis flaw, CVE-2026-90436, with an N-central privilege escalation weakness to gain root. A second set, Agent2Shell, can lead to code execution as root and SYSTEM-level access on Windows under certain conditions.

N-able's response

N-able is restricting some features and integrations. On hosted environments, the Legacy API is now off by default and Intune integration is disabled. The company says attackers are going after customers who haven't disabled the Legacy API.

Because N-central manages fleets of client machines, a compromised server can be a gateway to many downstream networks. A cryptominer today could be something worse tomorrow.

Who's affected

Managed service providers and IT teams running N-able N-central, hosted or on premises.

What to do

Upgrade Agents and Probes as N-able directs, confirm the Legacy API is disabled on premises, and hunt for the published indicators, including the 157.20.241.16 address and the jup.sh script. Treat any hit as a full compromise; Hotfix 2 alone isn't enough.

Tracked flaws:CVE-2026-90436