Skip to content

N-able confirms server breach in Mail Assure, SpamExperts cloud

N-able confirmed a server breach in its Mail Assure and SpamExperts Hosted Cloud, taking the portal, API, quarantine and logging offline. Mail flow unaffected; no customer-data evidence yet.

Published 3 min read

N-able says attackers gained unauthorized access to one of the servers in its Mail Assure and SpamExperts Hosted Cloud, the incident behind an outage that started November 16. The company first attributed the disruption to a "combination of platform configuration and service dependencies," then confirmed a day later that it was a security incident. N-able has not published a formal advisory; this is based on its status-page updates and reporting at BleepingComputer and The Hacker News.

What's affected

Mail Assure and SpamExperts Hosted Cloud, across the Americas, Asia-Pacific, and Europe. N-able says email flow and spam filtering kept running — the mail path itself was not interrupted. What went down is the control plane: the management portal, the API, quarantine, logging, and mailbox synchronization. Until those are restored, customers may be unable to sign in, release quarantined messages, review logs, or change domain settings.

In response, N-able disabled UI and API access, emailed customers, and says it is hardening the services against a repeat.

Data exposure

N-able says it has no evidence that customer data was compromised, including access to tenant mailboxes, and that the investigation is ongoing. As of the company's latest updates it had not described how the server was accessed or how long the attacker had a foothold. Treat "no evidence" as a provisional statement during an open investigation, not an all-clear.

What this is not

N-able states this is unrelated to the N-central incident that forced it to take hosted N-central environments offline to patch more than 30 zero-days in its RMM platform, and it has not linked the Mail Assure breach to the separately tracked 4EverAble2Shell zero-day used to drop cryptocurrency miners on N-central servers. The two product lines are distinct; conflating them overstates what N-able has confirmed.

Action checklist

  1. If you run Mail Assure or SpamExperts Hosted Cloud, read N-able's customer email and status page for your region rather than inferring state from the mail flow continuing to work.
  2. Do not rely on the portal, API, quarantine release, or logging until N-able confirms restoration — build a temporary process for anything that normally runs through them.
  3. Rotate any API keys or portal credentials once access is restored, given the control-plane components the attacker could reach.
  4. Preserve your own mail and authentication logs for the window since November 16; if N-able's logging was down, your side may be the only record.

Context

This is the third N-able story in short order, after the N-central zero-day wave and the 4EverAble2Shell server RCE. The common thread is managed-service infrastructure — RMM and hosted email security — sitting upstream of thousands of downstream tenants, where one provider-side compromise becomes everyone's incident. N-able's care to separate this breach from the N-central flaws is the right call, but the pattern of repeated provider-level exposure is the story operators should be tracking.

Related stories