INTELLIGENCEReference · public sources
← Incidents

Incident reportIdentity and email compromiseReport version 1 · November 21, 2026

Microsoft corporate email intrusion (Midnight Blizzard)

Microsoft disclosed that Midnight Blizzard compromised a legacy, non-production test tenant account through password spraying, then abused an OAuth application to access Microsoft corporate email accounts.

ReportedAttribution: Midnight Blizzard (APT29)Reference data · public sources

01Executive assessment

  • ReportedMicrosoft detected a nation-state attack on its corporate systems on January 12, 2024. [1]
  • ReportedThe actor compromised a legacy, non-production test tenant account that did not have multifactor authentication, using password spraying. [1]
  • ReportedA legacy test OAuth application with elevated access was used to grant access to Microsoft corporate email accounts. [1]

Implication: organizations in the affected sectors should confirm whether the access paths described in the sources apply to their own environment. A matching sector or technology is a reason to examine exposure, not evidence of compromise.

02What happened

Microsoft disclosed that Midnight Blizzard compromised a legacy, non-production test tenant account through password spraying, then abused an OAuth application to access Microsoft corporate email accounts.

Incident type
Identity and email compromise
Event period
January 12, 2024
Date precision
day
Evidence basis
Disclosure by the affected organization
Sectors
Technology

Detection date as stated by Microsoft. The start of the intrusion is not stated in the source.

03Evidence chronology

Publication dateDevelopmentTypeSource
January 12, 2024Microsoft detects the attack on its corporate systems.Detection (as stated)[1]
January 25, 2024Microsoft publishes responder guidance.Victim disclosure[1]

Event dates, source publication dates and our observation time (November 21, 2026) are recorded separately. Observation time is when DarkFire first collected the record, not when the activity occurred.

04Targets and geography

TargetRoleLocationPrecision and basis
MicrosoftAffected organization (self-disclosed)Redmond, Washington, United Statescity · Organization headquarters, affected system location unspecified

Locations describe affected organizations or countries as stated by the sources. They never indicate where an attacker operates from.

05Attribution assessment

Assessed by
Microsoft
Confidence
stated by source
Sources
[1]

DarkFire aggregates attribution published by the named assessing organization; it does not make its own attribution. Event evidence, actor attribution and location precision are separate judgments.

06Technical behavior

ATT&CKTechnique
T1110.003Password Spraying
T1098.001Additional Cloud Credentials
T1114.002Remote Email Collection

Techniques listed here are the behaviors described for this incident, not the actor's full ATT&CK catalog.

EVIDENCEACTOR AND TECHNIQUESMicrosoft Threat IntelligenceJanuary 25, 2024APT29 / Cozy BearMicrosoftPassword SprayingT1110.003Additional Cloud CredentialsT1098.001Remote Email CollectionT1114.002Microsoft

07Software and indicators

No publicly shareable indicators are recorded for this incident.

08Business exposure and priorities

Organizations in technology should review whether they share the conditions described in the sources: the same technology, supplier relationships or access paths. Relevance is a reason to examine exposure, not a finding of compromise.

The APT29 dossier sets out defender priorities for this actor's documented behaviors.

09Defensive actions

Inventory non-production tenants, dormant accounts and application identities alongside production users. Assign an owner and business purpose to each, remove access that is no longer required and examine high-privilege grants. Review device enrollment and session policies. These actions address the types of identity exposure described in the joint cloud advisory; implementation should account for the organization's actual services and authentication design.

Inspect supplier and application trust. Identify which providers can administer accounts, read mail or distribute software, and determine what evidence would reveal misuse. Retain identity and mail audit events in a form investigators can correlate across accounts and applications. During a suspected intrusion, evaluate consent grants, credentials, sessions and persistence together. A password reset addresses one mechanism and should not be treated as evidence that every access path has been removed.

From the APT29 dossier. For each action, name a control owner, the supporting evidence and a completion criterion.

10Analytic gaps

  • The start of the activity is not stated in the source.
  • The core claims rest on a single publishing organization; independent corroboration has not been recorded.
  • Whether access persists at any affected organization is unknown unless newer evidence is published.

11Source notes and changes

  1. [1]Midnight Blizzard: Guidance for responders on nation-state attackMicrosoft Threat Intelligence · published January 25, 2024 · collected November 21, 2026

Version 1, published November 21, 2026. No corrections recorded. Report an error to have it reviewed; corrections and retractions keep the previous version visible.