Rough month for N-able. After the N-central zero-days, the company disclosed on Wednesday that attackers got into a server behind Mail Assure and SpamExperts Hosted Cloud, its email filtering services used heavily by MSPs.
N-able says this is unrelated to the N-central flaws (Able2Shell, 4EverAble2Shell, Agent2Shell). Different product, different problem, same vendor having a very long November.
What We Know
Per The Hacker News, citing N-able:
- What happened: "unknown threat actors gained unauthorized access to one of the servers." N-able disabled management interfaces and APIs in response.
- Timeline: N-able started investigating a service disruption on November 16, first blamed on platform configuration and service dependencies. It was later determined to be a security incident. As of 8 a.m. UTC on November 19, restoration was still underway.
- Scope: Mail Assure and SpamExperts Hosted Cloud in the Americas, APAC and Europe.
- What's down: the management portal, APIs, quarantine and logging.
- What's up: core mail flow and inbound and outbound filtering.
- Customer data: N-able says "we do not have evidence that customer data was compromised." The investigation is ongoing.
- What N-able hasn't said: how the attacker got in, or who it was.
Credit where it's due: keeping mail flowing and filtering while pulling the management plane offline is the right trade. Email that stops is an outage for every customer. Email that keeps getting filtered while admins can't log in is an inconvenience. And calling it a security incident publicly, instead of leaving it as a "configuration issue," matters.
Why MSPs Should Care
An email security service sees every message for every customer. The quarantine is literally a pile of the most suspicious mail your clients received, plus some of the most sensitive mail that got caught by mistake. The management API can change filtering rules for many tenants at once.
So even without evidence of data access, the questions to ask are about the management plane, not mail flow: could someone have changed policies, added allow-list entries, released quarantined mail, or pulled API keys? Every vendor, mine included, has incidents. What matters is how much one compromised server can reach.
What To Do
- Read N-able's partner notice. N-able says it's contacting partners directly about whether action is required. Do what it says first.
- When the console comes back, review every tenant's config: allow-lists, routing rules, delivery destinations, outbound relay settings and admin users. Anything you didn't put there, take out and report.
- Rotate API keys and any credentials used by your PSA, RMM or automation tools to talk to Mail Assure or SpamExperts.
- Tell your clients what's going on, especially that quarantine release and log searches are unavailable, so their helpdesk isn't surprised.
- Expect phishing that uses this incident as a lure: "re-verify your Mail Assure account" emails are a predictable next step.
Bottom Line
The good news is that mail kept flowing and N-able says it has no evidence customer data was touched. The work for MSPs is checking that nobody quietly changed the rules while the lights were off.
Sources: The Hacker News, N-able status page