Hackers broke into one server inside N-able’s hosted email-security platform, and for days administrators across the Americas, Europe and Asia-Pacific lost access to the tools they use to manage client mail. N-able first told customers about a service disruption on November 16. It did not confirm a breach until November 18, after first blaming what it called “platform configuration.”

N-able sells remote IT and email-security products to managed service providers, or MSPs, which run them for many downstream clients at once. That model is why an outage in an admin layer reaches well past one company. Mail still moves through the affected products, but the people who set filtering rules, read logs and release quarantined messages for their customers have been locked out.

What the N-able breach confirmed so far

The company’s account changed in two steps. On November 17, N-able attributed the problem to platform configuration and service dependencies. On November 18, it revised that assessment and confirmed that unauthorized access had caused the disruption, according to GBHackers.

The intrusion touched one server in the Mail Assure and SpamExperts Hosted Cloud environment. N-able disabled management access across the Americas, Europe and Asia-Pacific while it investigated, according to Cybersecurity News. In a statement reported by SecurityWeek, the company said, “We have provided customers with specific guidance.”

N-able also says it found no evidence that customer data was compromised, including access to tenant mailboxes. That is the claim most customers care about most, and it comes from the company’s own investigation. N-able has not said who carried out the intrusion or what the attackers did on the server once they were inside.

Which N-able services are affected

Mail delivery and spam filtering kept running during the outage, according to The Hacker News. The disruption hit the management layer instead. Based on the reporting, the affected functions include:

  • The management portal and its APIs
  • Logging and mailbox synchronization
  • Quarantine tools, which hold messages that filtering has flagged
  • Admin access in all three regions

Mail Assure runs separate Americas, APAC and Europe instances, so customers should confirm which instance serves their domains instead of assuming a regional neighbor’s status applies to them.

The quarantine piece deserves attention. Attackers who control the admin layer of a filtering product can change rules or reach stored quarantined messages. N-able says mailboxes were not accessed. An independent analysis from The Cyber Security Guru notes that quarantined messages are kept for sixty days, which makes that store a sensitive target if the intrusion reached further than the company has described.

Why the N-able timeline has shifted

The timeline is not fully settled. N-able’s customer notice is dated November 16, but Mezha reported that the outage was first flagged on a Tuesday, which would be November 17. The gap matters because administrators who relied on the earliest message may have spent days with degraded control before they understood that an attack was possible.

Mezha also quoted N-able’s more direct explanation: “As we continued our investigation, we determined that the disruption was caused by a security incident.” That sentence reads as a correction of the earlier guidance rather than a separate event. Early vendor explanations for outages are worth checking against later statements, and this one changed within two days.

The people with the most at stake are small and midsize businesses that never chose N-able directly. They depend on an MSP, which depends on N-able. When the admin layer goes dark, the MSP has to explain to its clients why they cannot see quarantined mail or adjust filtering. Attackers have gained nothing that N-able has confirmed, but any intrusion into a shared filtering platform could, in principle, expose policy details across many customers at once.

How the N-central zero-day raises the stakes

N-able says the Mail Assure intrusion is unrelated to its N-central incident. That separate problem forced the company to take hosted N-central environments offline so it could patch more than 30 zero-day flaws, according to Mezha.

The N-central background goes back further. In August 2026, N-able disclosed a critical N-central flaw that affected all current versions, including 2026.3. In its September 2026 response notes, Huntress said the flaw was being exploited in the wild. Mezha also reported that BleepingComputer linked the N-central problem to a zero-day called 4EverAble2Shell, which BleepingComputer said was being used to deploy cryptocurrency miners on N-central servers.

For an MSP, that puts two problems on one vendor at the same time. One team may be patching N-central servers while another is checking email admin access and log integrity. N-able says the incidents are separate, but the timing means the same support staff may be handling both.

Admin consoles have become a repeat target. A VMware vCenter zero-day exploited since September showed how a management plane can become the way in. The Optimizely supply-chain attack that hit 178 sites showed how one vendor compromise can spread outward to every customer that trusts it.

What customers should check now

N-able has emailed Mail Assure and SpamExperts partners with environment-specific instructions on whether they need to act, according to CyberPress. Those emails are the first place to look. The steps below are general guidance, not a vendor checklist, so match them against what N-able tells you.

  1. If you use Mail Assure or SpamExperts Hosted Cloud, check N-able’s incident page and your partner emails for whether you need to act.
  2. Rotate admin and API credentials. N-able has not confirmed whether credentials were exposed, so treating them as possibly compromised is the safer call.
  3. Review admin and API logins from November 16 onward, and look for sign-ins or configuration changes you do not recognize.
  4. If an MSP manages your email, ask whether it uses these products, whether it was affected, and whether it has rotated its own keys.
  5. If your provider runs N-central, ask whether it has applied the zero-day patches before hosted environments come back online.

What N-able has not said yet

The open questions matter most. N-able has not named the attackers or described what they did on the server. It has not confirmed whether logins, API keys or tokens were exposed, and it has not said when full portal and API service will return. Remediation is still in progress, and none of the sources reviewed reports how many customers were affected.

What comes next

Watch three things. The first is whether N-able confirms or rules out credential exposure, because that decides whether customers must rotate keys across the board. The second is the date when the portal and API return, since MSPs cannot manage quarantine or filtering until they do. The third is whether N-able publishes a fuller timeline that explains the gap between its November 16 notice and the Tuesday flag.

Customers who manage clients through these tools should treat this as an open incident, not a closed one, until the company answers the credential question in writing.