Actively exploited Security news
Phishing campaign rides the Microsoft 365 outage with fake notices promising to 'restore held messages'
Microsoft Threat Intelligence on 16 November 2026 described a high-volume phishing campaign that piggybacked on the real global Microsoft 365 outage of 12–13 November. The emails, sent on 13 November, pose as service-health notices, claim that messages held during the outage will be deleted within 24 hours, and use a 'RESTORE MESSAGES' button to send victims to a third-party site. Microsoft assesses that the goal is most likely credential theft.
Key points
- The campaign started on 13 Nov 2026, a day after the real Microsoft 365 outage began. The emails mimic service-health notices referencing Exchange Online, Outlook, Teams, SharePoint and Copilot.
- They claim held messages will be deleted within 24 hours. 'RESTORE MESSAGES' and 'TAKE ACTION' buttons go through email-service tracking links to a non-Microsoft site.
- Microsoft did not directly observe credential submission or a phishing kit; it assesses credential theft as the likely goal. The campaign is not attributed.
- Defender for Office 365 blocks the messages, according to Microsoft, which also published domains, URLs, an IP address and advanced hunting queries.
What happened
On 16 November 2026, Microsoft Threat Intelligence warned of a high-volume phishing campaign it observed on 13 November. The attackers exploited the fact that a real global outage of Outlook, Teams and other services had started the day before, which we covered in Microsoft outage: Outlook, Teams and cloud down for ~18 hours. People were expecting delayed mail and recovery notices, and that is exactly what these emails imitate.
Technical details
The emails come from a cluster of sender domains and use bulk email delivery and click-tracking infrastructure (SendGrid). Display names include 'MSF Outage Notification' and 'AMZ Service Health'. Subjects end in a random token: Outage – aF7vG6, Strengthen – Security …, Restore — 4 messages …. One sample referred to an alleged Exchange Online incident on 12 November. The body also contains a hidden fake email thread intended to confuse filters.
Each recipient gets a unique tracking link that leads to a non-Microsoft domain, mainly reallifeaccounting[.]com. Microsoft has not observed credential submission itself, a phishing kit, attachments, QR codes or malware; it calls credential theft the most likely objective. The post does not mention adversary-in-the-middle (AiTM) session theft, and Microsoft does not attribute the campaign to any group.
Who is affected
Microsoft 365 organisations worldwide and across sectors. Microsoft gives no specific countries, industries or message volumes. The lure is generic, so it works anywhere people lived through the outage.
How to tell if you were hit
Indicators from Microsoft's blog (defanged; replace [.] with a dot):
Destinations: reallifeaccounting[.]com (principal destination)
outagefixed[.]sbs
outagerestored[.]sbs
URLs: hxxps://reallifeaccounting[.]com/themelist0[.]html
hxxps://outagerestored[.]sbs/topics_pxyk/themelist0[.]html
Sender/tracking: moments-notice[.]com, em4493.moments-notice[.]com
planetmaison[.]com
newbooker[.]com, em.newbooker[.]com, url.newbooker[.]com, url7489.newbooker[.]com
u113727626.ct.sendgrid[.]net, u118254266.ct.sendgrid[.]net, u118250677.ct.sendgrid[.]net
IP: 162.120.17[.]69:8080 (hosts /t/v3…/px.png)
Subjects: Outage – <random token>
Strengthen – Security <random token>
Restore — 4 messages <random token>
Defender XDR customers can find the campaign in Threat analytics under the same title as the blog post. Microsoft published three advanced hunting queries: messages by sender domain and subject (EmailEvents), messages containing campaign URLs (EmailUrlInfo) and user clicks (UrlClickEvents). The SendGrid hosts are shared and do not prove compromise on their own. Turn the list into detections with our IOC extractor, and check a suspicious link from an email with the Link checker.
What to do
- Hunt for the indicators in mail telemetry and quarantine or remove delivered copies (ZAP).
- Identify users who clicked and review proxy, endpoint and browser evidence.
- For potentially compromised accounts, reset passwords, revoke sessions and refresh tokens, and verify registered MFA methods.
- Review suspicious sign-ins, OAuth consents, inbox and forwarding rules, delegate permissions and unusual sharing.
- Block or monitor
reallifeaccounting[.]comand the/themelist0.htmlpath, but do not broadly block shared email infrastructure. - Tell staff that real service-health information lives in the admin center and never points to an outside site. Enable Safe Links and Safe Attachments and require phishing-resistant MFA (passkeys, security keys).
Timeline
- 12 Nov 2026 – global Microsoft 365 outage begins (about 18 hours, according to media reports).
- 13 Nov 2026 – Microsoft observes mass delivery of outage-themed phishing emails.
- 16 Nov 2026 – Microsoft Threat Intelligence publishes its analysis, indicators and hunting queries.
We verified these details on 17 Nov 2026 against Microsoft's Security Blog post of 16 Nov 2026.
FAQ
How do I tell a real outage notice from a fake one?
Genuine service-health notices never send you to a non-Microsoft site and never threaten to delete your mail. Check status yourself in the Microsoft 365 admin center (Service health), not through a link in an email.
I clicked the link but didn't enter anything. What now?
Report it to your IT team. Microsoft recommends reviewing proxy, endpoint and browser evidence. If you did enter your password, change it immediately and ask IT to revoke your sessions and check your MFA methods.
Should we block all sendgrid.net hosts?
No. Microsoft points out that the SendGrid hosts are shared infrastructure also used by legitimate senders. Block the destination domain and the /themelist0.html path, and weigh the other indicators alongside other signals.
Sources
Spotted a mistake? Let us know and we will correct it openly.