N-able Confirms a Breached Server in Mail Assure and SpamExperts Hosted Cloud. Mail Still Flows, the Console Is Dark. What MSPs Should Check When It Returns
If you are an MSP that routes customer mail through N-able Mail Assure or SpamExperts Hosted Cloud, do three things today. First, find N-able's direct notice to you. N-able says it contacted partners with "information relevant to their environment and whether action is required or not." If you did not get it, ask N-able support. Do not read silence as "not affected." Second, tell your customers that quarantined mail cannot be released for now. Third, when the console comes back, check every setting that decides where mail goes and who can change it, before you do anything else.
What is confirmed
N-able says an unauthorized party accessed one server in its Mail Assure and SpamExperts Hosted Cloud environment. N-able turned off management access while it investigates.
Here is the timeline from the reporting we read:
Monday, November 16, 2026: N-able began investigating a service disruption. It first traced the disruption to platform configuration and service dependencies.
Later, N-able decided the disruption was caused by a security incident.
Wednesday, November 19, 00:01 UTC: N-able began testing fixes in a controlled environment. The dashboard, quarantine, logging, mailbox synchronization and API access each have to pass security validation before they come back.
November 19, 08:00 UTC: restoration was still underway. No restoration time was given.
The affected services are Mail Assure and SpamExperts in the Americas, Europe and Asia-Pacific. Losing management access in all three regions does not mean a server was breached in each region. N-able has confirmed one server.
N-able's status page, as quoted by The Hacker News:
"We have taken steps to mitigate the threat and are continuing to harden our services to reduce the risk of recurrence."
"We do not have evidence that customer data was compromised, including access to tenants' mailboxes."
"The management portal (UI), APIs, quarantine, and logging remain offline while our teams work to restore them securely."
"Access will be restored once validation is complete."
Mail flow keeps working. Inbound and outbound filtering are running, so your customers can still send and receive email.
N-able says this incident is not related to the separate N-central incidents earlier this month.
What is not known
Who got in, how they got in, and how long they had access. N-able has not said.
Whether any credentials, API keys or tokens were exposed. N-able's public updates do not say so. One outlet's headline said N-able "warns of credential exposure." The body of that article says the public updates did not confirm any credential exposure, so the headline overstates it.
What N-able's direct notices to partners say. We have not seen one.
When the console, API, quarantine and logs will be back.
Indicators of compromise: none published in the sources we read. We have added nothing to our feed for this incident.
"No evidence that customer data was compromised" is the finding of an investigation that is still running. It is not a final result.
What to do now, while the console is offline
Find N-able's direct notice and follow it. This is the step that comes straight from N-able. It is the only source that says whether your environment needs action.
Tell customers that held mail cannot be reviewed or released yet. Expect tickets about "missing" email. Normal delivery does not tell you whether a given message was held.
Pause any automation that calls the Mail Assure or SpamExperts API, such as PSA sync, provisioning scripts or reporting jobs. The API is off, so these jobs will fail. Make sure a failing job does not retry in a loop or raise false alerts.
Do not treat working mail as a sign that management access is back.
What to check when access returns
N-able has not told everyone to reset credentials. The steps below are precautions. They follow from one fact: someone had access to a server inside the platform that holds your mail routing settings. Check them before you trust the console again.
Rotate the credentials for the platform: admin and sub-admin logins for your Mail Assure or SpamExperts accounts, and any API credentials or tokens your tools use. Do this after access is restored, and after reading N-able's notice in case it gives a specific order.
Review the list of admin users. Remove anyone you do not recognize.
Review the domain list. Look for domains you did not add, and domains that were removed.
Review delivery routes (the destination servers each domain delivers to). A changed route sends clean-looking mail to someone else's server.
Review outbound settings: smart host and relay users, and any outbound authentication. A new relay user can send mail that carries your customers' reputation.
Review allow-lists and block-lists (sender whitelists and blacklists) and filter rules. An added allow-list entry lets phishing skip filtering.
Read the logs from November 16 onward, once logging is back, for setting changes you did not make.
Check MX records at your DNS provider, not in N-able's console. Confirm each customer domain's MX still points where you expect. This is general hygiene: it lives outside N-able, but it is the setting an attacker most wants to change.
Check that customer mail servers still accept inbound mail only from the filter's addresses. General hygiene, and a quick win.
Audit integration tokens in tools that connect to the platform (PSA, RMM, billing). General hygiene: if a token is stored in two places, rotating it in one does not help.
Am I affected?
You are in scope if you or your customers use Mail Assure or SpamExperts Hosted Cloud in any region. The on-premises SpamExperts product is not named in the reports we read. To check your own exposure:
Search the inbox tied to your N-able partner account for N-able's notice since November 16. It says whether action is required for your environment.
When the Mail Assure or SpamExperts console is back, open the admin user list, domain list, delivery routes, outbound users and allow-lists, and compare each against your own records.
Open the logs for November 16 to the date access returns. Look for setting changes, new users or new API credentials you did not create.
At each customer's DNS provider, confirm the MX records match what you set up.
If all four match your records, you have no sign of a change. If anything does not match, treat it as an incident at that customer, and send it to N-able support.
How we know
N-able's status page for this event (uptime.n-able.com, event 202672) returned HTTP 403 to our reader. We could not read it directly. The N-able quotes above come from The Hacker News, which cites that status page. The timeline and other details come from Cybersecurity News, CyberPress and The Hacker News. All of them trace back to N-able's status page and its partner notices, so treat this as one source: N-able. We did not see a partner notice ourselves.
Sources
N-able status page, event 202672: https://uptime.n-able.com/event/202672/ (returned 403 to us)
The Hacker News, November 19, 2026: https://thehackernews.com/2026/11/n-able-confirms-hackers-accessed-cloud.html
Cybersecurity News: https://cybersecuritynews.com/n-able-confirms-server-breach/
CyberPress: https://cyberpress.org/n-able-confirms-cyberattack/
Read next
Another N-able product, N-central, had its own incident this month. That one has indicators you can hunt for: N-central 4EverAble2Shell Is Now Exploited: hunt for /tmp/.xvd and xvd.service
Every indicator in this post is in the feed. Free.
1.58M+ IOCs, STIX 2.1 / TAXII, 88% novel vs ThreatFox, exploited-CVE leads ahead of CISA. No credit card — a free API key in 30 seconds, and you can audit every claim above against the live endpoints.



Comments