Attackers Exploit Microsoft 365 Outage With Fake 'Restore Messages' Phishing Emails
Microsoft has identified a "coordinated, high volume" global phishing campaign built around the recent Microsoft 365 outage. The campaign was seen on November 13, while the company was still rolling out a fix for the failure that disrupted services such as Outlook and Teams worldwide. The outage began at 11.20 EST on November 12 and lasted more than 22 hours, with services fully restored at 23.15 EST on November 13.
The emails impersonated legitimate M365 service-health notifications. They claimed the recipient's emails had been held during the disruption and would be deleted within 24 hours unless action was taken, with a prominent "RESTORE MESSAGES" link to push people to click. Subject lines followed the pattern "Outage – <random token>", and display names combined a three-character, organisation-style prefix with "Outage Notification" or "Service Health". The messages referenced Exchange Online, Outlook, Teams, SharePoint and Copilot, and included fake email conversations hidden from the reader, which appears to be an attempt to evade mail filtering.
Clicking the link sent recipients to reallifeaccounting[.]com. Sender domains included moments-notice[.]com, planetmaison[.]com and newbooker[.]com. Microsoft said all observed messages were link-based, with no QR codes or attachments, and found no malware payloads. It judged the purpose to be credential phishing. There is currently no evidence of credential capture or post-compromise activity, and the campaign has not been attributed to a named threat actor.
Microsoft urged defenders to search mail telemetry for the sender domains, display-name and subject patterns, lure phrases and destination domain, then quarantine and remove matching messages. Teams should review click telemetry, proxy logs and endpoint evidence to see whether anyone clicked. For any user who may have entered credentials, reset passwords, revoke active sessions and refresh tokens.
Why it matters
Outages create a moment when staff are anxious and primed to follow instructions, which undermines the usual assumption that users will pause before clicking. Any organisation reliant on Microsoft 365 is exposed, and a fake notice that looks like routine service-health messaging is hard to spot by sight alone. Because Microsoft has seen no confirmed credential capture, the decision for defenders is whether to hunt for clicks now rather than wait for evidence of compromise.
What to do
- Search mail telemetry for the sender domains moments-notice[.]com, planetmaison[.]com and newbooker[.]com, and for subjects matching "Outage , <random token>".
- Quarantine matching messages and remove any that were already delivered.
- Block or closely scrutinise reallifeaccounting[.]com and the /themelist0.html path.
- Review click telemetry and proxy logs, then reset passwords, revoke sessions and refresh tokens for any user who may have entered credentials.