When a trusted email becomes a weapon: attacked in seconds, contained in six

On April 13, 2025, an attacker took over a Microsoft 365 account at an Oklahoma healthcare facility using an email from a real, trusted partner. Cloud security monitoring detected it and locked the attacker out in six seconds, before any patient data was compromised.

This is not a hypothetical scenario. The attack happened at a healthcare facility in Oklahoma that we support. The facility is not named here, and every detail is real.

"I can't open this Microsoft document. I put in my credentials but it won't open." That was the text the staff member sent to IT. She had no idea an attacker was already inside her account.

The email was real, and that is what made it dangerous

She was not careless, and she was not untrained. She did not click a strange link from a stranger. A clinical staff member received an email from a hospice partner she had worked with for years. Someone she trusted and emailed regularly. It was a real email, from a real person, at a real organization.

The problem was that the hospice organization's email account had already been compromised. The attacker was sending from that trusted account, using an existing relationship to get past every filter in place. No misspelled words. No odd sender address. No red flags, because it was not a fake email. It was a real account that had been turned into a weapon.

The email held what looked like a shared Microsoft document. She clicked through, entered her Microsoft 365 password and her multi-factor authentication code, and waited for the document to load. It never did. So she did what most people would do and texted IT. She thought it was a tech problem.

What the attacker did in the next ten seconds

This was not a person at a keyboard. It was an automated attack, a script built to take over an account, dig in, and start taking data before anyone noticed. Within seconds of getting access, the attacker:

Why the usual tools did not stop it

This organization had done the right things. It had spam filtering. It had MFA. It had endpoint security. None of that mattered here, because none of those tools are built to notice what happens after a login is stolen. Once the attacker was through the front door, those tools could not see them.

Without someone watching the Microsoft 365 environment itself, the attacker's behavior after login would have gone unnoticed for hours, days or weeks. Adding MFA devices, creating forwarding rules and reading the mailbox all look like normal account activity unless something is watching for exactly that.

In healthcare, that delay is costly. A compromised mailbox can expose protected health information, trigger HIPAA breach notification, and damage the trust of residents and families. A stolen Microsoft 365 account can also become a stepping stone toward clinical systems if those systems sit behind their own separate logins instead of single sign-on with conditional access.

Then the monitoring responded, in six seconds

Because this organization had invested in proactive cloud security monitoring, the attack never had the chance to do real damage. Before IT had even read the staff member's text, the monitoring had detected the unusual behavior and carried out an automated response:

The outcome

From the moment the login was entered to full containment and cleanup: six seconds. No sustained access. No evidence of data leaving beyond the first moments of access. The account was fully restored. No patient data was compromised.

By the time IT read her text and called her back, the attack was already over. That is when she said it: "I did not get phished. That was a valid email from someone I talk to all the time." She was right about the email. The damage had been done and undone inside six seconds.

What every organization should take from this

This staff member did nothing wrong. She answered a legitimate email from a person she trusted. That is the point. Training people to look for red flags does not help when the email is real, the sender is trusted and there are no flags to find. Your people cannot be the last line of defense. Your technology has to be.

If you use cloud email and nobody is watching it for what happens after a login, you have the same exposure this facility would have had. Firewalls and spam filters protect the edge. Attacks like this one happen inside, after the attacker is already through the door. Three questions are worth asking:

Common questions

She used MFA. How did the attacker still get in? The fake sign-in page passed her password and her MFA code straight to the attacker, who used them at once. MFA still stops most stolen-password attacks, but it does not stop this kind on its own. That is why monitoring what happens after login matters.

Was any patient information exposed? No. There was no sustained access and no evidence of data leaving beyond the first moments of access. The account was restored and no patient data was compromised.

Would security awareness training have prevented it? Probably not. The email came from a real partner's real account, with nothing suspicious to spot. Training is still worth doing, but it cannot be the only protection.

Can you tell us whether we are exposed the same way? Yes. A free account security checkup looks at how your cloud email is set up and whether anything is watching it after login. Call or text 405-285-3845.

Would you know in seconds, or in weeks?

A free 20-minute checkup of your Microsoft 365 or Google Workspace account shows which doors are open and whether anything is watching them.

Related reading

Contact UnityCare Technologies

Call or text: 405-285-3845

New customers: start@unitycareit.com

Existing customers: support@unitycareit.com

Service area: based in Edmond, Oklahoma, serving Oklahoma, Texas and Kansas

Hours: Mon–Fri 8 AM–5 PM CT; 24/7 after-hours support