What happened
Replaying the Healthplex November 2021 intrusion
- 1
A phished password
November 22 or 23, 2021A fax-themed phishing email reaches a customer service employee, and she enters her business email user name and password on the credential-harvesting site it links to.
- 2
A password-only web sign-in
November 24, 2021, about 06:00 CSTThe attacker signs in to the employee's Office 365 account through the office.com web application, which accepts the password alone because MFA is not enabled for Outlook Web Access.
- 3
Six hours in a twelve-year mailbox
November 24, 2021, about 06:00 to 11:58 CSTFor about six hours the attacker has access to a mailbox of over 100,000 emails dating back to May 2009, and the account sends phishing emails to other employees.
- 4
Found and closed the same day
November 24, 2021, about 11:58 CSTAfter the employees' reports, Healthplex resets the account's password and Azure account credentials and ends the access at about 11:58 CST.
For about six hours on November 24, 2021 an attacker had access to one customer service employee's Office 365 mailbox of over 100,000 emails (per DFS) dating back to May 2009, holding health data and personal information of tens of thousands of members; Healthplex notified 89,955 members on April 15, 2022. Which emails were opened, and whether any data left, could not be determined with the logging of the time. The account sent phishing emails to other employees, who reported them. No source says whether Azure or any other system was reached.
Where cloud-provider controls fit
In Microsoft Entra ID, a Conditional Access policy that requires multifactor authentication for all users on all resources, with a second one that requires it to register security information, would have stopped a phished password alone at your web sign-in; the Temporary Access Pass that lets a user with no method register under that policy became generally available in June 2022, after this incident. A Microsoft Purview retention policy that deletes old mail caps what a mailbox holds, not who reads it, and an outbound spam policy caps how many coworkers a taken-over account can mail before it is stopped. The lure and the password typed on another party's page sit with mail filtering and the endpoint, and here the reports and the reset came after about six hours of access.
Could this have been prevented?
In hindsight, not as a whole. 1 control would have refused a step outright, and 2 controls would have limited one. 3 steps have no cloud-provider control. The counts below are control assessments, not attack stages: several can address the same step. The same replay with the controls in place before the incident shows where each phase would have been refused or bounded.
- 1
- Prevented
- 2
- Contained
- 3
- Not covered
How it could have been prevented
The same replay with the controls in place. Green marks where a step is refused, blue where it is bounded, and red where no control reaches it. Open a row to read the control, why it acts, and its caveat.
Replaying the Healthplex November 2021 intrusion
1 · A phished password
2 Not covered2 · A password-only web sign-in
1 Prevented3 on other clouds3 · Six hours in a twelve-year mailbox
2 Contained4 · Found and closed the same day
1 Not coveredKey facts
- Earlier in 2021 Healthplex migrated its email to Office 365 and, per DFS, did not ensure that MFA was fully operational for web-browser access; its previous email environment had MFA
- On November 22 or 23, 2021 a phishing email offering a fax led a customer service employee to enter her business email user name and password on a credential-harvesting site
- On November 24, 2021 the attacker signed in through the office.com web application with the password alone and had access from about 06:00 to 11:58 CST, per the NYAG assurance
- The mailbox held over 100,000 emails per DFS, and nearly 130,000 needed review per NYAG, dating back to May 7, 2009 with no retention policy; Healthplex could not determine which emails were opened or whether any data left
- Employees reported phishing emails sent from the account the same day, and Healthplex reset the account's password and Azure account credentials and ended the access
- Healthplex notified 89,955 members, 63,922 of them New York residents, on April 15, 2022; NYAG announced a $400,000 settlement on December 11, 2023 and DFS a $2 million consent order on August 14, 2025
Sources
Every fact in this breakdown comes from the public reporting below. The replay is a model of that reporting, not a reconstruction of the environment it describes.
- 1.In the Matter of Healthplex, Inc. — Consent OrderNew York State Department of Financial Services · Aug 14, 2025 · Advisoryentry vector, sign-in without MFA, mailbox contents, discovery, regulatory report date, remediation, penalty
- 2.Assurance of Discontinuance No. 23-062, In the Matter of Healthplex, Inc.Office of the New York State Attorney General · Dec 11, 2023 · Advisoryentry vector, sign-in vector, access window, containment, mailbox contents, logging gap, counts, notification
- 3.Superintendent Adrienne A. Harris Secures $2 Million Cybersecurity Settlement with Healthplex, Inc.New York State Department of Financial Services · Aug 14, 2025 · Advisorypenalty, summary of findings
- 4.Email Security Incidents Reported by Healthplex and Optima DermatologyHIPAA Journal · May 9, 2022 · Newscompany notice paraphrase, count, notification date
- 5.NY AG Reaches $400K Settlement With Healthplex Over Data BreachTechTarget (Healthtech Security) · Dec 13, 2023 · Newssettlement, re-report of findings
The estate in the replay is illustrative and drawn at the level of attack stages; the victim's real environment is not public. Verdicts describe what a control does when it is in place before the incident. They are not an assessment of the victim's security program.