Incident · 8-K Item 1.05
Hewlett Packard Enterprise reports Midnight Blizzard access to cloud email
Compiled from public records. Updated 2026-11-12. By the cisonews.net Desk.
Hewlett Packard Enterprise filed an 8-K under Item 1.05 on January 24, 2024, reporting that a suspected nation-state actor had gained unauthorized access to its cloud-based email environment. The company says data was taken from a small percentage of mailboxes, and the filing gives no count of people or mailboxes affected.
Entries like this one, in Wednesday’s docket
Wednesdays
Unsubscribe any time.
What happened at HPE, and when?
HPE says it was notified on December 12, 2023 about the access, which it believes was the work of the group known as Midnight Blizzard, also called Cozy Bear. The company says it activated its response process with outside cybersecurity experts to investigate, contain and remediate the incident. Its investigation concluded that the data was accessed and exfiltrated beginning in May 2023.
Was the HPE breach linked to an earlier incident?
The filing says HPE now understands this incident is likely related to earlier activity by the same actor. HPE was notified of that activity in June 2023, and it involved a limited number of SharePoint files, with access as early as May 2023. After investigating with outside experts and taking containment and remediation steps, HPE determined at that time that the activity did not materially impact the company.
Was HPE hit by the same group as Microsoft?
HPE's filing names Midnight Blizzard. Five days earlier, on January 19, 2024, Microsoft had filed its own Item 1.05 report on a nation-state associated actor that reached senior leadership email accounts. Microsoft's filing does not name the actor. CISA's Emergency Directive 24-02 does: it says the Russian state-sponsored actor known as Midnight Blizzard took email correspondence between federal agencies and Microsoft by compromising Microsoft corporate email accounts. Neither company's 8-K mentions the other, and HPE does not say how the actor got into its email environment.
What data did the attackers take from HPE?
The filing does not list data types. It says the mailboxes belonged to individuals in cybersecurity, go-to-market, business segments and other functions. It does not say whether personal information of customers or employees was in the mailboxes or files, and it does not describe the contents of the SharePoint files.
Did the breach affect HPE's business?
HPE states that as of the filing date the incident had not had a material impact on its operations. It also says it has not determined that the incident is reasonably likely to materially affect its financial condition or results of operations.
How did HPE's investigation end?
HPE closed the matter in its annual report, not in an amended 8-K. Its first quarterly report after the disclosure, filed on March 5, 2024, still treated the incident as an open risk to its reputation and customer relationships. The annual report for fiscal 2024, filed on December 19, 2024, says the incident had been investigated and remediated, and that HPE had felt no material impact from it to date. The fiscal 2025 annual report, filed on December 18, 2025, no longer names the incident in its risk factors.
| Filing | Date | What it says |
|---|---|---|
| Form 8-K, Item 1.05 | January 24, 2024 | Disclosure; investigation and scope still open |
| Form 10-Q, Q1 fiscal 2024 | March 5, 2024 | Possible harm to reputation and customer relationships |
| Form 10-K, fiscal 2024 | December 19, 2024 | Investigated and remediated; no material impact to date |
| Form 10-K, fiscal 2025 | December 18, 2025 | Incident no longer named |
None of these filings says how many mailboxes were reached, what the exfiltrated data held, or what the response cost.
What is still unknown?
HPE describes its investigation of the incident and its scope as ongoing. It says it has notified law enforcement and is assessing its regulatory notification obligations, with notifications to follow as appropriate. The filing includes no notification letter, no call-center details and no enrollment deadline, and it does not say who will be notified.
How this disclosure's timing compares
Hewlett Packard Enterprise disclosed 43 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)
Sources
- 2024-01-24 · AHewlett Packard Enterprise Company, Form 8-K (SEC EDGAR), published January 24, 2024
- 2024-03-05 · AHewlett Packard Enterprise Company, Form 10-Q for the quarter ended January 31, 2024 (SEC EDGAR), published March 5, 2024
- 2024-12-19 · AHewlett Packard Enterprise Company, Form 10-K for fiscal 2024 (SEC EDGAR), published December 19, 2024
- 2025-12-18 · AHewlett Packard Enterprise Company, Form 10-K for fiscal 2025 (SEC EDGAR), published December 18, 2025
- 2024-01-19 · AMicrosoft Corporation, Form 8-K, Item 1.05 (SEC EDGAR), published January 19, 2024
- 2024-04-02 · ACybersecurity and Infrastructure Security Agency, Emergency Directive 24-02, published April 2, 2024
- 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.