Skip to content
cisonews.net

Incident · 8-K Item 1.05

Microsoft discloses nation-state access to senior leadership email accounts

Compiled from public records. Updated 2026-11-12. By the cisonews.net Desk.

Microsoft disclosed in a Form 8-K filed with the SEC on January 19, 2024 that a nation-state associated threat actor had accessed and taken information from a very small percentage of its employee email accounts, detected on January 12, 2024. The accounts included those of senior leadership team members and staff in cybersecurity, legal and other functions, and the filing gives no count of people affected.

Entries like this one, in Wednesday’s docket

Wednesdays

Unsubscribe any time.

What happened at Microsoft, and when?

Microsoft says the access began in late November 2023. The company reports that it found the activity on January 12, 2024. It removed the actor's access to the email accounts on or about January 13, 2024. The filing describes the findings as resting on preliminary analysis.

Who was behind the Microsoft email breach?

Microsoft's SEC filings call the intruder only a nation-state associated threat actor. The Cybersecurity and Infrastructure Security Agency (CISA) names it. Its Emergency Directive 24-02, issued on April 2, 2024, says the Russian state-sponsored actor known as Midnight Blizzard took email correspondence between federal civilian agencies and Microsoft by compromising Microsoft corporate email accounts.

The same group appears in another company's filing that month. Hewlett Packard Enterprise filed its own Item 1.05 report on January 24, 2024, five days after Microsoft's. It says a suspected nation-state actor, believed to be Midnight Blizzard, had reached its cloud-based email environment. Neither company's 8-K mentions the other.

What did CISA order federal agencies to do after the Microsoft breach?

CISA's directive says the actor was using what it had taken from the corporate email systems, including authentication details that Microsoft customers had shared with Microsoft by email, to gain or try to gain more access to customer systems. Citing Microsoft, it adds that some parts of the campaign, such as password sprays, grew by as much as 10-fold in February compared with January 2024.

The directive required affected agencies to:

  • act at once on any token, password, API key or other credential known or suspected to be compromised;
  • by April 30, 2024, reset those credentials, deactivate applications no longer in use and review sign-in and token logs;
  • by April 30, 2024, identify the full content of their correspondence with the compromised Microsoft accounts and analyze its cybersecurity impact;
  • report status to CISA by April 8, 2024 and update it by May 1, 2024.

Microsoft and CISA notified every federal agency whose email correspondence with Microsoft was identified as taken. CISA has since closed the directive, saying its purposes had been met.

What did the attackers take from Microsoft?

The filing does not list data types. It says Microsoft was still reviewing what was taken. It also says regulators are being told about unauthorized access to personal information, without saying whose or what kind. The company says it has notified law enforcement.

Did the breach affect Microsoft's business?

At the original filing, Microsoft said operations had not been materially affected. It had not yet reached a view on financial condition or results. The amendment repeats the same position as of March 8, 2024.

What did Microsoft's March 2024 amendment add?

The 8-K/A reports that the actor moved beyond email. Microsoft says it determined the actor used information it obtained to try to reach other systems. It characterized the activity as ongoing and sustained. The company also warned that more access was possible. It said it had raised its security investments in response.

What do Microsoft's later reports say?

Microsoft's quarterly reports fill in what the 8-Ks left out. The 10-Q filed on April 25, 2024 names the method: beginning in late November 2023, the nation-state associated actor used a password spray attack to compromise a legacy test account, and from there reached Microsoft email accounts. The same report says the actor had used, and was still using, what it obtained to gain, or try to gain, access to some source code repositories and internal systems.

By the 10-Q filed on January 29, 2025, the wording is firmer and in the past tense: the actor used the information it obtained to gain unauthorized access to some of Microsoft's source code repositories and internal systems, and may keep using it to try to get in. Microsoft also says the incident has harmed, and may keep harming, its reputation and customer relationships.

FilingWhat it says about the source code and internal systems
8-K/A, March 8, 2024The actor used information it obtained to try to reach other systems
10-Q, April 25, 2024Used and still using the information to gain, or try to gain, access
10-Q, January 29, 2025Used the information to gain unauthorized access

Microsoft's annual reports carry the same account. The 10-K filed on July 30, 2024 says the actor "used and may continue to use" what it obtained to gain, or try to gain, access to source code repositories and internal systems. The 10-Ks filed on July 30, 2025 and July 29, 2026 use the past tense: the actor used the information to gain unauthorized access, and could keep using it to try to get in. The fiscal 2026 report still cites the incident as an example in its risk factors, more than two years after the 8-K. That differs from HPE, whose fiscal 2025 annual report no longer names its Midnight Blizzard incident.

Annual reportFiledHow it describes the access
10-K, fiscal 2024July 30, 2024Used and may continue to use the information to gain, or try to gain, access
10-K, fiscal 2025July 30, 2025Used the information to gain unauthorized access; could try again
10-K, fiscal 2026July 29, 2026Same wording as fiscal 2025

What is still unknown?

None of the filings states how many accounts or people were affected beyond the percentage wording, which email contents were taken, or which source code repositories or internal systems were reached. Neither says whether individual notification letters were sent.

How this disclosure's timing compares

Microsoft disclosed 7 days after the discovery date its filing gives. Across the 46 other filings under 8-K Item 1.05 on cisonews.net that date discovery to the day, the median gap is 6 days.

The rule behind an Item 1.05 filing

Form 8-K Item 1.05 is where a public company reports a cybersecurity incident it has determined to be material. Under the rule the SEC adopted on July 26, 2023, the filing is generally due four business days after the company determines that the incident is material. Source: U.S. Securities and Exchange Commission, press release 2023-139. The guide What is SEC Form 8-K Item 1.05, and what counts as a disclosed cyber incident? reads the rule in full, and the glossary defines Form 8-K Item 1.05.

Other technology incidents on cisonews.net

  • DreamHost, Breach notice, first disclosed November 2, 2026
  • Photon Health, Breach notice, first disclosed October 28, 2026; affected: approximately 1706 Rhode Island residents
  • Indico Data Solutions, Breach notice, first disclosed October 27, 2026; affected: 79 Rhode Island residents
  • Stitch Connect Inc, Breach notice, first disclosed September 21, 2026; affected: 113,727 people in total (Indiana AG record)
  • IDScan.net, Breach notice, first disclosed September 18, 2026; 27,624 affected in total (Indiana Attorney General)

All technology incidents

Sources

  1. 2024-01-19 · AMicrosoft Corporation, Form 8-K (SEC EDGAR), published January 19, 2024
  2. 2024-03-08 · AMicrosoft Corporation, Form 8-K/A (SEC EDGAR), published March 8, 2024
  3. 2024-04-25 · AMicrosoft Corporation, Form 10-Q for the quarter ended March 31, 2024, published April 25, 2024
  4. 2025-01-29 · AMicrosoft Corporation, Form 10-Q for the quarter ended December 31, 2024, published January 29, 2025
  5. 2024-04-02 · ACybersecurity and Infrastructure Security Agency, Emergency Directive 24-02, published April 2, 2024
  6. 2024-01-24 · AHewlett Packard Enterprise Company, Form 8-K, Item 1.05 (SEC EDGAR), published January 24, 2024
  7. 2024-07-30 · AMicrosoft Corporation, Form 10-K for fiscal 2024 (SEC EDGAR), published July 30, 2024
  8. 2025-07-30 · AMicrosoft Corporation, Form 10-K for fiscal 2025 (SEC EDGAR), published July 30, 2025
  9. 2026-07-29 · AMicrosoft Corporation, Form 10-K for fiscal 2026 (SEC EDGAR), published July 29, 2026
  10. 2023-07-26 · AU.S. Securities and Exchange Commission, press release 2023-139, published July 26, 2023

Tier A: the organization itself (including notices it filed with a state attorney general), a regulator or SEC EDGAR. Tier B: established press. Each fact on this page carries its supporting passage in the page source.

Entries like this one, in Wednesday’s docket

Wednesdays

Unsubscribe any time.