Skip to content
Security & Trust

N-able says mail filtering kept running, but customers lost the portal for days

After a breach at Mail Assure and SpamExperts, N-able says filtering stayed on while the portal and API went dark. Its first explanation also changed.

W
WebPulse Newsroom
AI-assisted · 4 min read
Share on X LinkedIn
N-able says mail filtering kept running, but customers lost the portal for days

Graphic: WebPulse, drawn from the sourced facts in this story.

In brief
  • N-able says an attacker accessed one server in its Mail Assure and SpamExperts Hosted Cloud, after first blaming configuration. It reports no evidence that customer data or mailboxes were reached.
  • N-able says mail filtering kept running, but customers lost the portal, API, quarantine and logs. It says dashboard and API access was restored on November 21.
  • Ask your provider what you can still see and change when its management layer is offline, and how quickly it tells you the true cause.

The mail flowed. The people who run it were locked out.

A security incident can leave a service working and still leave its customers blind. That is the lesson of N-able's recent trouble with Mail Assure and SpamExperts Hosted Cloud, two hosted products that filter email for businesses and the partners who manage them.

N-able says that inbound and outbound filtering kept running throughout. What went offline was the layer people use to watch and steer the service. That layer is the management portal, the API, quarantine and logs.

What N-able says happened

On November 16, N-able told customers about a service disruption. Its early update blamed a mix of platform configuration and service dependencies. It said it believed it had fixed the problem.

By November 18, the company had changed its account. A notice on its status page now said the disruption came from a security incident, and it confirmed "unauthorized access to one of the servers" in the Hosted Cloud environment.

On the question of customer data, N-able said it had found no evidence of compromise. That includes tenants' mailboxes. The company added that its investigation is ongoing. That describes what has been found so far, not a final finding.

The company also said the incident is unrelated to a separate N-central incident. BleepingComputer, which covered the story, describes that other matter as one that led N-able to pull its hosted N-central environments offline while it fixed more than 30 zero-day flaws. N-able's statement of separation is the company's own.

N-able says it disabled the portal and API on purpose while it investigated. On November 21 at 23:44 UTC, it reported that dashboard and API access had been restored in phases. It said it would watch the platform for about another hour. It also said further customer communication would follow.

Why losing the control layer hurts

Think of an airport whose planes keep landing while the control tower goes dark. Flights continue. Nobody can see the board, change a route or answer a question.

N-able describes the same gap. Until the services returned, customers could not sign in to the control panel or view and release quarantined messages. They could not review logs or change settings, such as adding or removing domains.

Each of those is a daily task. A legitimate invoice stuck in quarantine cannot be released. A new domain cannot be added. A team investigating a suspicious message has no log to read. Mail gets through, but the people responsible for it work without their tools.

The recovery was also slow, and N-able's own updates show why. On November 17, before it disclosed the breach, the company said the fix meant rebuilding infrastructure and updating parts of the platform. From November 19 onward, its updates said each service had to pass security validation in a controlled environment before it came back.

The explanation that changed

The second lesson is about the first statement. N-able's early account pointed to configuration and dependencies. Its later account named unauthorized access. The company says that came from continued investigation.

That is not unusual in an incident. The early cause of a disruption is often a guess. For a customer, the practical question is what to do with an explanation that may change. A team that treated the first update as the answer would have started with a wrong picture.

The sources do not say how the attacker got in, who they were or what they did on the server. They also do not say when N-able first learned of the intrusion. Nothing here supports a claim about motive or method. What the sources do support is narrower and still useful: a hosted security product can be breached, and its customers may learn that in stages.

What to ask your team and your provider

Start with dependence. Which of your email security or other hosted tools have a management layer you cannot reach without the vendor? List what your staff could still do if that layer were off for several days.

Next, ask about records. Do you keep your own copy of the logs and settings you would need to investigate a message, or do they live only in the vendor's portal?

Then ask about communication. If you use a partner or managed provider for N-able products, check whether they received the direct email N-able says it sent. N-able says partners who did not receive it should contact its technical support.

Finally, ask how fast your provider revises its account. A vendor that corrects its account is better than one that does not. A buyer still needs to know how quickly the correction will reach them.

The product that protects the inbox is also a system with its own doors. When it fails, the question is not only whether mail still arrives. It is whether you can still see, and still steer.

Produced by the WebPulse Newsroom with AI assistance from the original reporting credited below, and checked against that source by our editorial review. How we use AI.
Original reporting: N-able.