Skip to content

Threat Actors

Microsoft warns of high-volume phishing campaign using M365 outage lures

Microsoft said the Nov. 13 campaign pretended to be service-health notices and claimed held email would be deleted within 24 hours.

https://breach-signal.com/threat-actors/microsoft-warns-phishing-campaign-m365-outage-lures/

Share

Key facts

  • Microsoft assessed the activity as likely credential phishing but said available evidence did not show credential capture, malware delivery, or follow-on compromise.
  • The company did not assign the activity to a specific threat group or malware family.
  • The outage began at 11.20 EST on November 12 and lasted more than 22 hours, with full restoration confirmed at 23.15 EST on November 13.
  • The subject pattern was Outage – <random token>. Display names combined a three-character organization-style prefix with Outage Notification or Service Health.

Microsoft Threat Intelligence observed a coordinated, high-volume phishing campaign on Nov. 13, 2026, aimed at organizations in multiple industries around the world. “We assess that the activity was likely credential phishing; however, the available evidence does not confirm credential capture,” Jeremiah Jasmin, security researcher at Microsoft, said. The company tied the activity to no specific threat group or malware family. The campaign also reached organizations in multiple US sectors.

SecurityWeek reported that an outage on Nov. 12 cut access to Exchange Online mailboxes and Outlook, with possible effects on Teams, SharePoint Online, and Microsoft 365 Copilot, and that groups and government bodies across multiple countries said email and other work faced interruptions. The interruption began at 11.20 EST on Nov. 12 and lasted more than 22 hours, according to Infosecurity Magazine, with full restoration confirmed at 23.15 EST on Nov. 13. Microsoft tracked the failure as EX1550543 and marked it resolved on Nov. 13. “This was a technical issue not related to cyber or AI / agents,” Microsoft said in a statement on Friday.

The messages masqueraded as legitimate Microsoft 365 service-health notices and warned that held e-mail would be deleted within 24 hours unless recipients acted. Messages carried subjects built around Outage – <random token>, and display names merged a three-character organization-style prefix with Outage Notification or Service Health. Sender domains included planetmaison.com, newbooker.com, and moments-notice.com, and links sent users to reallifeaccounting.com and reallifeaccounting.com/themelist0.html. One sample cited a purported Exchange Online incident on Nov. 12 and claimed four messages were held after the outage.

The messages invoked Exchange Online, Outlook, Teams, SharePoint, and Copilot. The messages also included a concealed false e-mail thread in the message body, a tactic assessed as an effort to bypass mail filtering. The operation used links only, with no QR codes or non-EML attachments, and researchers uncovered no executable, archive, document, or other malware payload. The operation used e-mail delivery and link-tracking infrastructure to build recipient-specific URLs.

Malicious domains are blocked by Microsoft Defender, and Defender for Office 365 blocks and quarantines the phishing messages. The company urged blocking or close monitoring of reallifeaccounting.com and the /themelist0.html path during the investigation, while cautioning against broad blocks of shared email-delivery infrastructure. The campaign exhibited MITRE ATT&CK, a framework for classifying adversary behavior, techniques T1566.002 spearphishing link, T1036 masquerading, and T1204.001 malicious link; Microsoft found no mapping for credential capture or malware execution, nor for command and control or data exfiltration.

Defenders should scan mail telemetry for sender domains, subject and display-name patterns, lure language, tracking hosts, and the destination domain, then isolate and remove matches. Security teams should identify users who clicked campaign links and review click telemetry, proxy records, and browser or device evidence. For users who may have entered credentials, organizations should reset passwords, revoke active sessions, rotate tokens, and confirm multifactor authentication registrations. Check accounts for suspicious sign-ins, altered OAuth consent, mailbox or forwarding rules, delegate permissions, and atypical access to Exchange Online, SharePoint, OneDrive, or Teams.

If users entered credentials, organizations faced exposure through cloud collaboration data, internal phishing, business e-mail compromise, mailbox access, and compromised accounts. Microsoft Security Copilot customers can use prebuilt promptbooks for incident investigation and for analyzing users who selected campaign links.

Organizations should require multifactor authentication, prefer phishing-resistant methods such as passkeys or security keys, enable Safe Links and Safe Attachments, and switch on Zero-hour auto purge, Microsoft said. Microsoft also urged administrators to run attack simulation training and instruct users to report suspicious messages through the organization’s current Outlook reporting process. Real Microsoft 365 service-health notices never send users to non-Microsoft sites to recover held mail; confirm issues in the Microsoft 365 admin center.

Microsoft said multiple threat actors are likely to keep exploiting notable global events in social-engineering pretexts, in line with historical campaigns. “This is consistent with historical attacker campaigns which continuously look for notable global events to exploit in their social engineering lures,” Microsoft said in a blog dated November 16.

Devroop Dhar, co-founder and MD at Primus Partners, said outages breed uncertainty and panic that attackers exploit. He pointed to finance, health care, government, and educational institutions as especially exposed, since their employees handle sensitive data and depend on cloud services. He advised folding cybersecurity into business continuity planning, increasing monitoring during disruptions, running phishing simulations amid outages, and holding tabletop exercises.

Was this helpful?

Join the discussion

Please read our Comment Policy before commenting. First-time comments are held for moderation. By posting a comment you agree to our Terms of Use and Privacy Policy, which explain how your name, email address and comment are used.

Your email address will not be published. Required fields are marked *