The short version
- The breach. N-able says unknown attackers gained unauthorised access to one of the servers in the Mail Assure and SpamExperts Hosted Cloud. The company disabled the management interfaces and APIs in response and says it is hardening the services.
- Services affected. Mail Assure and SpamExperts are both listed as impacted in the Americas, APAC and Europe. N-able says core mail flow and inbound and outbound mail filtering remain available.
- Customer data. N-able says its investigation is ongoing and that at this point it has no evidence customer data was compromised, including access to tenants' mailboxes.
- How it surfaced. N-able opened an investigation into a service disruption on 16 November. It first attributed the disruption to platform configuration and service dependencies, then determined it was caused by a security incident.
Timeline
| Date | Event |
|---|---|
| 16 November | N-able begins investigating a service disruption affecting the Mail Assure and SpamExperts Hosted Cloud. |
| 18 November | N-able discloses that unknown attackers accessed one of the servers in the hosted cloud and takes management interfaces and APIs offline. |
| 19 November | At 08:00 UTC N-able says restoration is still under way, with work continuing to validate and harden the management portal. |
What N-able has said
N-able disclosed on 18 November that unknown attackers had gained unauthorised access to one of the servers in its Mail Assure and SpamExperts Hosted Cloud. It said it had taken steps to mitigate the threat and was continuing to harden the services. The management portal, APIs, quarantine and logging were taken offline, while N-able says core mail flow and inbound and outbound filtering stayed available.
The disclosure followed a service disruption that N-able began investigating on 16 November. The company initially traced it to a combination of platform configuration and service dependencies inside the hosted environment, and later concluded the disruption was actually caused by a security incident. N-able says access to the management interface will return once validation is complete.
Who is affected
The company lists six impacted services: Mail Assure and SpamExperts in each of the Americas, APAC and Europe. Organisations using these services to filter mail therefore lose the portal, API access, quarantine and logging for now, even where filtering itself keeps working.
N-able says it has contacted Mail Assure and SpamExperts Hosted Cloud partners directly with information relevant to their own environment and whether any action is required. The company says it has no evidence that customer data was compromised, a finding it describes as holding at this time while the investigation continues.
Unrelated N-central flaws
The report of the hosted cloud intrusion is separate from several vulnerabilities found in N-able's N-central product, which are referred to as Able2Shell, 4EverAble2Shell and Agent2Shell. The source says the hosted cloud incident is unrelated to those flaws, and nothing in it links the two.
What is not known yet
- Who carried out the intrusion and how they obtained access to the server.
- How many customers or tenants were affected, and in which regions they sit.
- Whether any mailbox or message content was viewed, beyond N-able's statement that it has no evidence of data compromise.
- When the management portal, APIs, quarantine and logging will be restored.
- Whether the attackers had access before the disruption was noticed on 16 November.
What to do
If you use Mail Assure or SpamExperts Hosted Cloud
- Check the direct communication N-able says it has sent to partners, which states whether action is required in your environment.
- Assume the management portal, APIs, quarantine and logging are unavailable until N-able confirms validation is complete, and do not build workflows that depend on them.
- Confirm through your own mail logs that inbound and outbound filtering is still processing your traffic, since the vendor's own logging is offline.
If you rely on another hosted email security provider
- Map which functions — filtering, quarantine, portal access, logging — sit with the third party rather than in your own infrastructure.
- Rehearse how you would review and release held mail if the provider's portal were unavailable.
- Keep an independent source of mail visibility so that losing vendor logging does not leave you without records.
For everyone else
- Record which of your security controls are delivered as a hosted service, so a provider-side breach or outage is treated as an availability and access risk to your organisation, not only to the vendor.
Update log
- First published.
Sources
New incident reports by email
One email a week with the reports published since the last one.
We email you about this topic only; unsubscribe any time. See our Privacy Policy.