Phishing emails posing as Microsoft 365 outage notices ask staff to restore held mail
Microsoft has published its own findings on a high-volume campaign using the November 12 Outlook and Exchange Online outage as a lure, complete with the real incident ID.
By Junglewise News Desk. Published . Updated
If your staff could not send email on November 12 and then got a message offering to recover the mail that was stuck, treat it with suspicion. Microsoft has now published its own write-up of the campaign, a blog post titled "High volume phishing campaign uses Microsoft 365 outage lures to target multiple industry sectors", confirming that its threat intelligence team tracked attackers using the outage as bait against organizations in multiple industry sectors worldwide.
The trick works because the story is true. The outage disrupted Exchange Online and Outlook, with possible knock-on effects for Teams, SharePoint Online and Microsoft 365 Copilot, and the fake emails quote the genuine Exchange Online incident ID, EX1550543. For a small business with no security team, that is the uncomfortable part: the lure matches something your people actually experienced, so the usual instinct that something looks off is weaker than normal.
The disruption ran well over a day. It began around 11:20 EST on November 12 and ran for more than 22 hours, with services fully restored by 23:15 EST on November 13, Infosecurity Magazine reported. Businesses and public bodies in a number of countries said their email and other day-to-day operations were knocked out while it lasted.
Microsoft has said the outage itself was not an attack. "This was a technical issue not related to cyber or AI / agents", the company said according to SecurityWeek, tracing it to an earlier network capacity upgrade that a later network change exposed. The Exchange Online incident was marked resolved on November 13.
What is not settled is how much damage the phishing has done. Microsoft says the activity looks like credential phishing (emails designed to steal usernames and passwords) but that it has not confirmed credentials were captured. "We assess that the activity was likely credential phishing; however, the available evidence does not confirm credential capture, malware delivery, or post-compromise activity," Microsoft security researcher Jeremiah Jasmin said, as reported by Computerworld. Microsoft has not attributed the campaign to any named group or malware family, and says it has seen no evidence of account compromise tied to it so far.
What to do now
- Tell staff what the lure looks like, today. The messages claim emails were held during the outage and will be deleted within 24 hours unless the recipient clicks a link to restore them. One analyzed message said four messages were being held and offered a "RESTORE MESSAGES" button. Deadline pressure plus a familiar incident number is the whole trick.
- Make the verification rule simple. Check service incidents in the Microsoft 365 admin center, not from a link in an email. Microsoft's advice is that legitimate service-health notices do not send people to non-Microsoft domains.
- Search your mail for the indicators. Microsoft suggests hunting email telemetry for the sender domains, the display-name and subject-line patterns, the lure wording, the tracking hosts and the destination domains listed below, then quarantining or removing anything that matches.
- Check clicks, not just deliveries. Microsoft's guidance is to investigate whether users interacted with the messages rather than only whether the mail was delivered. Review click telemetry, proxy logs and endpoint or browser evidence for anyone who followed a link.
- If someone clicked and entered a password, reset it, revoke active sessions and tokens, and confirm multi-factor authentication is in place and has not been altered.
- Look for the signs of a mailbox takeover. Suspicious sign-ins, unauthorized OAuth app consent, new inbox or forwarding rules, added mailbox delegates, and unusual access to Exchange Online, SharePoint, OneDrive or Teams.
- Block the destination. Microsoft advises blocking or monitoring
reallifeaccounting[.]comand the/themelist0.htmlpath while you investigate. - Review your Safe Links policies while you are in the console.
If anything does land, watch for the follow-on: internal phishing from a compromised mailbox and invoice fraud. Any payment or bank-detail change that arrives by email should be confirmed on a phone call to a number you already had.
Technical details
There is no CVE here. This is social engineering, not a software flaw, and no patch applies.
Lure and message structure. Phishing emails impersonate Microsoft 365 service health notices and reference the real incident EX1550543. Messages detected on November 13 claimed held mail would be deleted within 24 hours. Subject lines started with Outage - followed by a six-character code; sender display names combined organization-specific wording with Outage Notification or Service Health. The bodies referenced Exchange Online, Outlook, Teams, SharePoint and Copilot, and carried "RESTORE MESSAGES" call-to-action links. Computerworld reported that the attackers embedded a fake hidden email conversation in the body to slip past filtering.
Infrastructure. Microsoft named three sending domains: moments-notice[.]com, planetmaison[.]com and newbooker[.]com. Recipient-specific SendGrid tracking links redirected to reallifeaccounting[.]com, with recipients landing on that domain or on reallifeaccounting[.]com/themelist0.html.
Payload. Link-based only. No QR codes and no executable, archive or document malware were observed, and no non-EML attachments were used.
Timeline. The outage began around 11:20 EST on November 12 and lasted over 22 hours, with full restoration by 23:15 EST on November 13. The Exchange Online incident, EX1550543, was marked resolved on November 13, the same day the phishing messages were detected. Microsoft published its blog post on the campaign on November 16.
Status. Microsoft says its security products are blocking the campaign, with messages blocked or quarantined by Defender for Office 365. The scale of any successful credential theft is unknown, and so is who is behind it. Microsoft has noted only that the activity is consistent with past campaigns that use notable global events as social-engineering lures.
Devroop Dhar, co-founder and managing director of Primus Partners, told Computerworld the uncertainty around an outage leaves staff exposed. "This is especially dangerous for industries like finance, health care, government and educational institutions because employees in such organizations work with sensitive data and rely heavily on cloud services", he said. His broader suggestion is a reasonable habit for any business: treat a major technology disruption as a cue to raise monitoring, run a phishing simulation during the disruption, and rehearse the response in a tabletop exercise before you need it.
What changed
- : Added the full outage timeline and Microsoft's own November 16 blog post confirming the phishing findings, and removed indicators not confirmed by Microsoft.