← All playbooks
HighBreach · 2026-11-20

N-able Mail Assure and SpamExperts breach: attacker accessed a hosted-cloud server, portals and APIs still offline in all regions

SockAnalyst · Security+ certified analyst.

What happened

N-able says an unauthorized party accessed one server in the Mail Assure and SpamExperts Hosted Cloud, the email filtering services it sells to managed service providers (MSPs). Its status page shows the incident starting at 03:00 UTC on November 17, 2026 (customers were first told of a service disruption on November 16), first blamed on platform configuration and service dependencies; at 03:05 UTC on November 18 N-able said the disruption was in fact a security incident. N-able told SecurityWeek the intrusion was isolated to a single web server where the attacker may have been able to access certain credentials stored on the platform, and that it took the server offline, rotated internal platform credentials, revoked existing customer API tokens, invalidated OAuth tokens and reset passwords for local users. It says it has no evidence that customer data or tenant mailboxes were accessed, the investigation is ongoing, and the incident is unrelated to the N-central Able2Shell attacks. As of its November 20 update (08:06 UTC), mail flow and inbound/outbound filtering work, but the management portal, APIs, quarantine, logging and mailbox sync remain disabled. N-able has not said how the attacker got in, how long they had access, or who it was.

Who's affected

MSPs and their customers using N-able Mail Assure or SpamExperts Hosted Cloud in any region. Mail still flows, but admins cannot release quarantined mail, review logs, change domains, or use API-driven integrations, and any integration using a revoked API or OAuth token will need new credentials once access returns. Expect phishing that impersonates N-able, Mail Assure or SpamExperts 'restore access' notices.

✅ Fix / patch

  • Read the direct email N-able sent each Mail Assure/SpamExperts partner about whether action is needed in your environment; if you did not get it, contact N-able Technical Support (per N-able's status page). Follow uptime.n-able.com for restoration.
  • Plan for revoked credentials: N-able says it revoked customer API tokens, invalidated OAuth tokens and reset local user passwords. When access returns, issue new tokens, store them in a secrets vault, and remove the old values from scripts, PSA/RMM integrations and documentation.
  • Assume any secret you stored in the platform (for example mailbox-sync or outbound SMTP credentials and API keys) may have been exposed until N-able says otherwise: rotate those credentials on your side and check the related accounts for unusual sign-ins.
  • While quarantine and logging are offline, use your mail platform's own message trace (Microsoft 365 / Exchange / Google Workspace) to watch what is being delivered, and warn end users and help desks about fake N-able or Mail Assure notices.

🔎 Quick hunt check

N-able has published no IOCs, no root cause and no attacker details. These hunts check the exposure around the incident, not this attacker's signature: (1) inbound mail mentioning N-able, Mail Assure, SpamExperts or quarantine release that does not come from N-able's real domains; (2) sign-ins or API calls using mailbox-sync or SMTP relay service accounts that were configured in Mail Assure/SpamExperts, from unusual IPs since Nov 16; (3) a sudden change in delivered spam/phishing volume through the filtering connector while you cannot see its logs.

MITRE ATT&CK: T1199, T1552.001, T1078, T1566.002

IOCs

No IOCs (IPs, domains or hashes) published by the sources yet.

Hunt queries

Starting points built only from published indicators. Field names vary; tune before use.

```N-able Mail Assure/SpamExperts breach: lookalike N-able notices, unusual use of mail service accounts since Nov 16```
index=* earliest=11/16/2026:00:00:00
(sourcetype=*mail* OR sourcetype=*o365* OR sourcetype=*azure*signin* OR tag=email OR tag=authentication)
| eval sender=lower(coalesce(src_user, sender, from, SenderAddress, "")), subj=coalesce(subject, Subject, "")
| eval acct=lower(coalesce(user, UserPrincipalName, "")), ip=coalesce(src_ip, src, ClientIP, "")
| eval signal=case(
    match(subj,"(?i)n-able|mail ?assure|spam ?experts|quarantine (release|report)|restore (access|service)") AND NOT match(sender,"@([a-z0-9-]+\.)*(n-able\.com|spamexperts\.com)$"), "lookalike_nable_notice",
    match(acct,"(?i)mailassure|spamexperts|mailsync|mail-sync|smtp-relay|smtprelay"), "mail_filter_service_account_activity",
    true(), null())
| where isnotnull(signal)
| stats count min(_time) as first_seen max(_time) as last_seen values(subj) as subjects values(ip) as ips values(action) as actions by signal, sender, acct
| convert ctime(first_seen) ctime(last_seen)
| sort - count
``` Replace the service-account pattern with the exact accounts you configured in Mail Assure/SpamExperts ```
// N-able Mail Assure/SpamExperts breach: lookalike N-able notices + sign-ins by mail-filter service accounts since Nov 16
let Since = datetime(2026-11-16);
let SvcAccounts = dynamic(["mailassure","spamexperts","mailsync","smtprelay"]); // replace with your real service account UPN fragments
union isfuzzy=true
(EmailEvents | where TimeGenerated >= Since
 | where EmailDirection == "Inbound"
 | where Subject has_any ("N-able","Mail Assure","MailAssure","SpamExperts","quarantine release","restore access")
 | where not(SenderFromDomain has_any ("n-able.com","spamexperts.com"))
 | summarize Hits = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated), Evidence = make_set(Subject, 20) by Who = SenderFromDomain
 | extend Signal = "lookalike_nable_notice"),
(SigninLogs | where TimeGenerated >= Since
 | where UserPrincipalName has_any (SvcAccounts)
 | summarize Hits = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated), Evidence = make_set(strcat(IPAddress, " ", tostring(LocationDetails.countryOrRegion), " ", ResultType), 20) by Who = UserPrincipalName
 | extend Signal = "mail_filter_service_account_signin")
| order by LastSeen desc

See all hunt queries →

⏱ CISA deadline

Not in CISA KEV as of Nov 22, 2026.

Sources

Related playbooks

Get the SockAnalyst Weekly Brief free, every Thursday.

One email a week with the KEV deadlines, patches and hunt queries that matter. New playbooks still post here on the site every morning.

Subscribe free

Read the free weekly pack →