Skip to main content

N-able’s Mail Assure Outage Was a Cyberattack on One Server, and Partners Lost Portal and API Access for Days

N-able says hackers reached one server behind Mail Assure and SpamExperts, and the outage first blamed on configuration was a security incident. Mail kept flowing; the portal and API did not. What partners and their customers should check.

KBY News Desk7 min read
Person using a laptop to read an email indoors beside a potted plant.

N-able has confirmed that hackers got into one web server behind its Mail Assure and SpamExperts hosted email-filtering services, and that the multi-day outage which began on Monday 16 November was a security incident, not the configuration fault the company first described. Mail flow and filtering kept working throughout. What did not work was everything a managed service provider (MSP) uses to run the product: the management portal, the APIs, quarantine and logging. The most recent update we could read, from Friday 20 November, said portal and API access was still switched off as a precaution. We could not find a later one.

We are writing this as analysis because the facts have mostly settled since the company’s statements between 18 and 20 November, and because the useful part for readers is what to do while access is still limited. N-able says the incident is unrelated to the N-central vulnerabilities we covered earlier this month, and says it has no evidence that customer data, including tenants’ mailboxes, was compromised.

#What N-able has said, in order

The disruption began on Monday 16 November. N-able’s first explanation, as both SecurityWeek and The Hacker News report it, was “a combination of platform configuration and service dependencies”. By Wednesday 18 November the company had changed its account: an unauthorised party had accessed one server in the Mail Assure and SpamExperts Hosted Cloud, and N-able had disabled the management interfaces and APIs in response. The Hacker News lists six affected services: Mail Assure and SpamExperts, each in the Americas, Asia-Pacific and Europe regions.

N-able told SecurityWeek that the incident “was isolated to a single web server, where an unauthorized party may have been able to access certain credentials stored on the platform”. It listed what it did next: it took the server offline, rotated internal platform credentials, revoked existing customer API tokens, invalidated OAuth tokens and proactively reset passwords for local users. On 20 November, at 08:06 UTC, the company said its engineers were working through remaining remediation items and that portal and API access was still disabled as a precaution, according to The Hacker News.

Two details are worth holding apart. The company says there is no evidence that customer data was compromised. It also says an unauthorised party “may have been able to access certain credentials stored on the platform”. Those two sentences can both be true, and the second is the one that should drive your actions. Daily Security Review notes that N-able has not said how the attackers got in or how long they had access, and we have seen nothing from N-able that fills that gap.

#Who is affected, and how

If your business buys email filtering from an IT provider, there is a fair chance that provider runs it on Mail Assure or SpamExperts, Daily Security Review says the people most affected are the MSPs that resell and administer the product. For their customers, the visible effect was small: email carried on being scanned and delivered. For the MSPs, the effect was larger. Without the portal and APIs, partners could not change filtering policies, review quarantined messages or pull logs for the tenants they manage.

The API detail matters for a second reason. N-able says it revoked existing customer API tokens. Any integration that called the Mail Assure API with an old token, such as a script, a ticketing or billing connector, or a monitoring check, will fail until a new token is issued, and tokens can only be issued once the portal and API return. That is our reading of what revocation means in practice, rather than something N-able has spelled out, but it follows from the company’s own description and it will catch people out when access returns.

#What to check this week

  1. Find out whether you use it. Ask your IT provider, in these words: “Is our inbound email filtered by N-able Mail Assure or SpamExperts, and have you received N-able’s guidance for our tenant?” N-able says it contacted partners directly with “information relevant to their environment and whether action is required or not”, and told SecurityWeek it gave customers “specific guidance based on how they access and configure” the services. If you are the customer of a provider, that message may not have reached you.
  2. List every credential you gave the service. If you stored a password, key or connection detail in the portal, for a directory link, a mail-server connection or an integration, treat it as a candidate to rotate. We cannot tell you which items sit on the affected server, because N-able has not said, so assume the worst case and ask for the specific list.
  3. Plan for quarantine without a portal. If a legitimate message is stuck in quarantine, nobody can release it through the portal at the moment. Tell staff how to reach you for an urgent release, and expect your provider to ask N-able for help on specific messages.
  4. Do not assume a link to the N-central incident. N-able says the two are unrelated. If you run N-central, our earlier report on the N-central zero-days covers that separate problem, which needs its own patching.
  5. Watch for phishing that uses the incident as bait. Messages claiming to reset your Mail Assure password or “verify your quarantine” are the obvious lure. Reset instructions should come from your provider, through a channel you already trust, never from a link in a message.

#If you are a small business

You probably did not choose Mail Assure, and you may not know it sits in front of your mailboxes. The one thing to do is send your IT provider the question above and ask for the answer in writing. If they confirm you are affected, ask three follow-ups: whether any passwords or keys that your setup stored in the service need changing, whether anything in your email configuration changed during the incident, and when the portal will be back. A good provider will answer all three the same day. If yours cannot, that tells you something about their process.

#Our view: containment was sound, the explanation was slow

We think N-able made two good decisions and one poor one. Keeping filtering running while pulling the management layer offline protected the part of the service every customer depends on, and rotating credentials and revoking tokens is what you do when you cannot rule out that secrets were read. The poor one was the first explanation. Calling an incident “platform configuration and service dependencies” and then correcting it about two days later leaves partners making decisions on a wrong premise for the period when the choices matter most. A vendor that suspects an intrusion can say so as a possibility without declaring it proven.

The pattern is also worth noticing. In our reading, tools that MSPs use to run many customers at once are an attractive target, because one foothold can reach many organisations. We covered that in our coverage of attacks on ConnectWise ScreenConnect technicians and in the N-central zero-days. This incident is a different vendor system with a separate cause, so we are not saying the events are connected, only that the same buyers should ask the same question of every tool in the chain: what does it hold on my behalf, and who can reach it?

#What we expect next

We expect the portal and API to come back with forced credential resets and new API tokens, and we expect N-able to publish more detail on the entry route once its investigation closes. We would be wrong if the portal stays offline for another week, which would suggest the hardening work is bigger than the company has said, or if N-able later reports that stored credentials were in fact used. If either happens, partners should expect to rotate more than they planned and to hear it from N-able directly. We will update this story when the company publishes a restoration notice or an incident report.

Evidence trail

Sources and verification

Primary documentation and external technical references used in this article.

  1. 01SecurityWeek: N-able Blames Service Disruption on Cyberattack (20 November 2026)securityweek.com
  2. 02The Hacker News: Hackers Breach N-able Cloud Server, Disrupting Email Security Management Across 3 Regions (19 November 2026, updated 20 November)thehackernews.com
  3. 03Daily Security Review: N-able Confirms Breach of Mail Assure and SpamExperts Cloud Server (19 November 2026)dailysecurityreview.com

About this page

Credited to

Dates

Published

Corrections

No corrections are listed for this page. Some review sweeps corrected pages without naming each one; those are in the corrections log.

Reader Interaction

Comments

Add a thoughtful note on N-able’s Mail Assure Outage Was a Cyberattack on One Server, and Partners Lost Portal and API Access for Days. Comments are checked for spam and held for moderation before appearing.

Loading comments...

Get new fixes by email.

New runbooks, configuration traps and fixes from KBY Technologies, about twice a week.