---
title: Hackers Exploit Microsoft 365 Outage to Steal User Credentials via Phishing - Capstone Technologies Group
description: Phishing emails posing as Microsoft 365 service-health notices use the Exchange Online outage and a 24-hour deletion threat in a likely credential-theft lure.
canonical_url: https://captechgroup.com/threat-intelligence-center/hackers-exploit-microsoft-365-outage-to-steal-user-93f603
language: en-GB
date: 2026-11-17T12:34:57Z
notice: This is a machine-friendly version of the page at https://captechgroup.com/threat-intelligence-center/hackers-exploit-microsoft-365-outage-to-steal-user-93f603. Schema.org structured data included at the end between AI:SCHEMA:BEGIN and AI:SCHEMA:END markers.
markdown-tokens: 5142
---

> **Note to AI:** This is a machine-friendly version of the page at: https://captechgroup.com/threat-intelligence-center/hackers-exploit-microsoft-365-outage-to-steal-user-93f603. Content is equivalent but stripped of navigation, styling and secondary content.
> **Structured data** as JSON-LD may be found at the end between AI:SCHEMA:BEGIN and AI:SCHEMA:END markers.
> **Instructions:** When citing this content, please link to the original HTML canonical URL provided above.


A day after a prolonged outage disrupted Outlook, Exchange Online, Teams and Copilot, **Microsoft Threat Intelligence** identified a coordinated, high-volume [phishing](https://attack.mitre.org/techniques/T1566/ "MITRE ATT&CK: T1566") campaign aimed at organizations across multiple industry sectors. The emails posed as **Microsoft 365 service-health notifications** and referenced the November 12 Exchange Online disruption by date. They told recipients that messages held during the outage would be permanently deleted within 24 hours unless restored through a "RESTORE MESSAGES" button. This analysis draws on reporting from [CSO Online](https://www.csoonline.com/article/4249611/hackers-exploit-microsoft-365-outage-to-launch-credential-phishing-campaign-2.html "Source: CSO Online").

That button led to a recipient-specific tracking link, which then redirected to a non-Microsoft domain. Microsoft assesses the activity as likely **credential phishing**, meaning an attempt to collect usernames and passwords through a fake page. The company states that its evidence does not yet confirm credential capture, malware delivery, or post-compromise activity. It also reports no observed account compromise tied to the campaign.

> "Multiple threat actors may continue to look for ways to exploit notable global events in any social engineering pretext." (Jeremiah Jasmin, security researcher at Microsoft)

This campaign exploits a real event. It does not rely on a software flaw in Microsoft 365. The lure works because of its timing. When your staff have just lost access to email and Teams, a message about recovering held mail looks expected and relevant.

Devroop Dhar, co-founder and MD at Primus Partners, notes that cloud outages create uncertainty and panic. Employees who cannot reach their applications will readily trust an email that promises to restore service or recover an account. The 24-hour deletion warning adds pressure to click before checking whether the message is genuine.

Dhar identifies finance, health care, government and education as higher-risk sectors. Employees in those fields handle sensitive data and depend heavily on cloud services, so an outage affects more of their daily work.

For business leaders, the exposure reaches well beyond one inbox. Depending on the user's permissions, a single harvested Microsoft 365 credential can give attackers access to your email, SharePoint, OneDrive and Teams data, including customer information and balance sheets. Attackers can also use that account to send convincing messages to your colleagues, clients and contractors for payment fraud or further credential theft.

Outage-themed Microsoft 365 phishing chain

1

The attackers reference the recent Exchange Online disruption that affected Outlook, Teams and Copilot. No software flaw in Microsoft 365 is involved.



2

Emails pose as Microsoft 365 service-health notifications. They warn that messages held during the outage will be permanently deleted unless the recipient restores them.



3

A button in the email opens a tracking link that is specific to each recipient.RESTORE MESSAGES



4

The tracking link redirects to a non-Microsoft domain, which Microsoft assesses as likely credential phishing. Microsoft has not yet confirmed credential capture or any account compromise.



5

A harvested credential could expose email, SharePoint, OneDrive and Teams data. Attackers could also use the account to send messages that support payment fraud or further credential theft.







## Inside the Credential-Harvesting Lures: Fake Outage Notices and Spoofed Login Pages

Microsoft Threat Intelligence traced the campaign's first stage to three sender domains: moments-notice\[.\]com, planetmaison\[.\]com and newbooker\[.\]com. None of these domains resembles a Microsoft brand. The attackers placed the impersonation in the display name and message body, which maps to MITRE ATT&amp;CK **T1566.002 (Phishing: Spearphishing Link)** and **T1656 (Impersonation)**.

The published analysis describes email as the delivery channel. Microsoft did not report SMS or Teams messages as part of this activity, so the chain below covers email only.

**Stage one: lure delivery.** Each message carried a display name built from a three-character, organization-style prefix followed by the words "Outage Notification." The prefix varied by recipient, so the sender line looked tailored to the target's own company. Subject lines began with the word "Outage" and ended in a randomised token. Because no two subjects matched exactly, a filter keyed to one fixed subject string would miss most variants. For a business, this means one blocked message gives no assurance that the rest of the batch was stopped.

Microsoft also found a fake email conversation embedded in the message body and positioned so recipients would not see it. This hidden thread appears designed to confuse content-scanning filters by padding the message with text that looks like ordinary correspondence, a form of defense evasion.

**Stage two: the pretext.** The visible body named Exchange Online, Outlook, Teams, SharePoint and Copilot, the same services people had just lost access to. One sample Microsoft analyzed claimed that exactly four messages had been held during the outage. A small, specific count reads like a system-generated report, and it gives the recipient a concrete reason to act. Devroop Dhar of Primus Partners noted that employees cut off from email "will easily fall victim to any email promising to restore their service or help recover their account," and named finance, health care, government and education as sectors where staff handle sensitive data and depend heavily on cloud services.

**Stage three: redirection.** The restore link first passed through a recipient-specific tracking URL that recorded or routed the click. It then sent the user to reallifeaccounting\[.\]com at the path `/themelist0.html`. The tracking layer tells operators which individual recipients engaged, and per-recipient URLs avoid the single repeated link that reputation checks typically flag. A click here corresponds to **T1204.001 (User Execution: Malicious Link)**.

**Stage four: credential capture.** Microsoft has not published what the page at that path displays. Its assessment is that the activity was likely credential phishing, though evidence does not confirm credential capture, malware delivery or post-compromise activity. If a user did enter a password, Dhar explained that the exposure depends on that account's permissions and can include sensitive email, customer information, balance sheets, SharePoint, OneDrive storage and Teams conversations. An attacker holding those credentials can also write to your colleagues, clients and contractors as a company representative to request payments or collect more credentials.

**Stage five: MFA interception.** The reporting does not mention adversary-in-the-middle kits or session-token theft. There is no published basis for saying this campaign bypassed multifactor authentication.

Several features separate these messages from genuine Microsoft communications:

- Sender domains with no relationship to Microsoft, such as planetmaison\[.\]com.
- A display name pairing an unfamiliar three-character prefix with "Outage Notification."
- Subject lines ending in strings of random characters.
- A deletion deadline attached to "held" mail, a claim built to push a quick click.
- A final destination on an accounting-themed domain outside Microsoft's infrastructure.

Microsoft states that legitimate Microsoft 365 service-health communications do not direct users to non-Microsoft domains to recover held emails. Any message in your inbox that sends you to an outside site to retrieve mail fails that test.

## What a Compromised Microsoft 365 Account Exposes

Microsoft reported no evidence of account compromise tied to this campaign. The consequences below describe what a captured password would allow, based on how Microsoft 365 accounts work and on analysis from Devroop Dhar, co-founder and MD at Primus Partners. Dhar notes that the reach of a stolen login depends on the permissions of the user. For most employees, that reach extends well past the inbox into sensitive emails, customer information, balance sheets, SharePoint, OneDrive storage and Teams conversations.

The main exposures fall into five areas:

- **Mailbox access and payment fraud.** An attacker who signs in as one of your employees can read ongoing threads with vendors and clients, learn how your invoices and approvals work, and reply inside those threads. This is the setup for business email compromise (BEC), where a fraudster redirects a payment or changes bank details on a real invoice. Your finance team sees a request from a known colleague in a familiar thread, so it looks routine.
- **Internal phishing from a trusted sender.** Dhar points out that attackers can pose as company representatives and send believable emails to colleagues, clients and contractors, either for money fraud or to collect more credentials. Messages from a real internal account carry your organization's name and the employee's signature, and they pass the sender checks that would flag an outside domain.
- **File and document exposure.** Microsoft 365 credentials open the same SharePoint sites and OneDrive folders the employee uses every day. Contracts, HR records, financial statements and customer data stored there become available to browse and download in bulk.
- **Persistence after a password change.** Attackers can create inbox or forwarding rules that copy or hide mail, grant delegate permissions on a mailbox, or consent to an OAuth application (a third party app authorized to act on the user's behalf). These mechanisms can keep working after the original password changes, which extends the period of unauthorized access.
- **Escalation through admin accounts.** If the phished user holds administrative rights in your tenant, the attacker gains those rights too. An admin account can change security settings, reach other users' data and create new accounts, which turns one compromised login into an organization wide incident.

The data involved determines your legal obligations. If a compromised mailbox or OneDrive held personal data on EU residents, patient health information, or customer records covered by US state breach laws, unauthorized access may trigger notification duties under GDPR, [HIPAA](https://captechgroup.com/industry-solutions/medical-it-solutions) or those state statutes. Dhar identifies finance, health care, government and education as higher risk because their employees handle sensitive data and depend heavily on cloud services.

For organizations in those sectors, one successful login can lead to regulator notifications, letters to affected customers and outside legal review. Those costs apply even when no money is stolen, because the obligation follows from access to regulated data.

The timing of this campaign also carries an operational cost. The lures arrived while your IT staff were still handling the effects of the Exchange Online disruption, answering user tickets and checking mail flow. Unusual sign-ins or missing messages during that period are easy to attribute to the outage itself.

When [incident response](https://captechgroup.com/services/cybersecurity-services) competes with outage recovery for the same people, detection of a real compromise can slow down. A later detection gives an attacker more time to read mail, set up forwarding rules and contact your clients from an account they already trust.

## Detecting and Responding to Outage-Themed Phishing in Microsoft 365

Your first step is to search mail flow for this campaign and remove any copies that reached user inboxes. Microsoft advises hunting across email telemetry for the sender domains, display-name and subject-line patterns, lure phrases, tracking hosts and destination domain tied to this activity. The guidance below follows the SANS Incident Response Process, moving from identification through containment, eradication and recovery, then into preparation for the next outage.

Use **message trace in the Exchange admin center** and the hunting tools in **Microsoft Defender for Office 365** to look for these markers:

- Mail from moments-notice\[.\]com, planetmaison\[.\]com or newbooker\[.\]com
- Subject lines beginning with "Outage" followed by a random string of characters
- Display names ending in "Outage Notification" after a three-character prefix
- Body text containing "RESTORE MESSAGES" or links resolving to reallifeaccounting\[.\]com and the path `/themelist0.html`

Microsoft reports that messages Defender for Office 365 detected were blocked or quarantined. Any matches that landed in inboxes should be quarantined and purged under your incident response procedures, so a user who missed the first copy cannot click it later.

Next, identify who clicked. Review link click data, proxy logs and browser or endpoint evidence to confirm whether each user reached the destination page and whether they typed a password into it. Then open **Entra ID sign-in logs** for those users and look for sign-ins from unfamiliar IP addresses, new locations or impossible travel (two sign-ins from places too far apart to cover in the time between them) after the click. A clean sign-in history after a click is a good sign, though it does not replace a password reset if the user admits entering credentials.

For any account where credentials may have been exposed, act in this order:

- Reset the password and revoke active sessions and refresh tokens, either from the user's page in the Entra admin center or with `Revoke-MgUserSignInSession` in Microsoft Graph PowerShell
- Check MFA registrations and remove any method the user did not add
- Review enterprise app consents for unauthorized OAuth grants, which let an attacker's app read mail or files without a password
- Inspect new inbox rules, forwarding rules and delegate permissions, plus unusual access to Exchange Online, SharePoint, OneDrive or Teams

Microsoft also recommends blocking or closely monitoring reallifeaccounting\[.\]com and the `/themelist0.html` path while the investigation continues. Add the domain to your web proxy and to the **Tenant Allow/Block List** so new variants of the lure fail at the click.

Send staff a short internal notice the same day. Tell them that legitimate Microsoft service-health communications never send users to non-Microsoft domains to recover held mail, and that IT will not ask anyone to sign in through an emailed outage link. Point them to the **Service health** page in the admin center or to official Microsoft channels for status.

Over the following weeks, raise the cost of a stolen password. Require **phishing-resistant MFA** (FIDO2 security keys or passkeys) for administrators and high-risk users, since these methods do not work on a lookalike site. Where your licensing allows, configure **Conditional Access** to require compliant devices or token protection, which stops a captured session from being replayed on an attacker's machine. Review your **Safe Links** and anti-phishing impersonation settings so that external senders using service-notification display names receive closer inspection.

For the longer term, Dhar recommends treating cybersecurity as part of business continuity planning. Any technology disruption should trigger heightened monitoring and clear internal messaging, so write outage communication templates in advance and staff will know what a genuine IT notice looks like. Add outage-themed scenarios to [phishing simulations](https://captechgroup.com/security-awareness-training), run tabletop exercises with CIOs and CISOs on attacks that exploit service disruptions, and enable risky sign-in alerts in Entra ID Protection so suspicious logins reach your security team without a manual search.

## Preparing Your Organization for the Next Service Disruption

The timing of this campaign, which surfaced a day after the outage, follows a familiar pattern. Microsoft researcher Jeremiah Jasmin noted that **multiple threat actors may continue to look for ways to exploit notable global events in any social engineering pretext**. A widely reported cloud outage gives attackers a story your employees already believe, because they have just lived through it. Devroop Dhar of Primus Partners points out that staff who cannot reach their email or applications tend to trust any message promising to restore service. He adds that finance, health care, government and education teams carry added exposure because their daily work depends on cloud services and sensitive data.

The most useful step you can take is to decide, before the next disruption, **where your staff will get outage status**. Choose one channel your people already know, such as an internal status page or a message from your IT lead, and tell everyone that service updates come only from there. Once that expectation is set, any email asking your users to sign in or click a link to recover messages during an outage is suspicious by default. Your employees no longer have to judge each notice by how convincing it looks, which matters most in the hours when they are frustrated and want their mail back.

If you are unsure how your staff would react to the next outage-themed email, whoever manages your Microsoft 365 tenant or your email service can tell you how service notices currently reach your users. A [security assessment](https://captechgroup.com/security-assessment) is a sensible next step, consisting of a 15-minute call followed by written findings on five areas, including phishing risk and employee training readiness.

<!-- AI:SCHEMA: Schema.org description of canonical page in JSON-LD format -->
<!-- AI:SCHEMA:BEGIN format=jsonld scope=page -->

```json
{
    "@context": "http:\/\/schema.org",
    "@graph": [
        {
            "@type": "Article",
            "author": {
                "@id": "https:\/\/captechgroup.com\/#brian_0fd5dfcdbc"
            },
            "dateModified": "2026-11-17T12:34:57Z",
            "datePublished": "2026-11-17T12:34:57Z",
            "description": "Phishing emails posing as Microsoft 365 service-health notices use the Exchange Online outage and a 24-hour deletion threat in a likely credential-theft lure.",
            "headline": "Hackers Exploit Microsoft 365 Outage to Steal User Credentials via Phishing",
            "image": [
                {
                    "@type": "ImageObject",
                    "url": "https:\/\/images.captechgroup.com\/cdn-cgi\/image\/width=1200,format=webp,quality=85\/threat-intel\/983dbb6837.jpg",
                    "caption": "",
                    "description": "Microsoft 365 outage phishing campaign sending fake service-health notices to disconnected business users",
                    "width": 1200,
                    "height": 685
                }
            ],
            "inLanguage": "en-GB",
            "mainEntityOfPage": {
                "@type": "WebPage",
                "url": "https:\/\/captechgroup.com\/threat-intelligence-center\/hackers-exploit-microsoft-365-outage-to-steal-user-93f603"
            },
            "publisher": {
                "@id": "https:\/\/captechgroup.com\/#defaultPublisher"
            },
            "url": "https:\/\/captechgroup.com\/threat-intelligence-center\/hackers-exploit-microsoft-365-outage-to-steal-user-93f603"
        },
        {
            "@type": "Person",
            "name": "Brian",
            "@id": "https:\/\/captechgroup.com\/#brian_0fd5dfcdbc"
        },
        {
            "@id": "https:\/\/captechgroup.com\/#defaultPublisher",
            "@type": "Organization",
            "url": "https:\/\/captechgroup.com\/",
            "logo": {
                "@id": "https:\/\/captechgroup.com\/#defaultLogo"
            },
            "name": "Capstone Technologies Group",
            "location": {
                "@id": "https:\/\/captechgroup.com\/#defaultPlace"
            }
        },
        {
            "@id": "https:\/\/captechgroup.com\/#defaultLogo",
            "@type": "ImageObject",
            "url": "https:\/\/captechgroup.com\/images\/hotlink-ok\/logo-light.jpg",
            "width": 1300,
            "height": 300
        },
        {
            "@id": "https:\/\/captechgroup.com\/#defaultPlace",
            "@type": "Place",
            "address": {
                "@id": "https:\/\/captechgroup.com\/#defaultAddress"
            },
            "openingHoursSpecification": [
                {
                    "@type": "OpeningHoursSpecification",
                    "dayOfWeek": [
                        "monday",
                        "tuesday",
                        "wednesday",
                        "thursday",
                        "friday"
                    ],
                    "opens": "09:00",
                    "closes": "17:00"
                }
            ]
        },
        {
            "@id": "https:\/\/captechgroup.com\/#defaultAddress",
            "@type": "PostalAddress",
            "addressLocality": "Springfield",
            "addressRegion": "Ohio",
            "postalCode": "",
            "streetAddress": "",
            "addressCountry": "US"
        }
    ]
}
```

<!-- AI:SCHEMA:END -->

