← Blog

Changing the password doesn't remove the laptop the attacker added

Tenant Strike2 min read

In a campaign against 79 organizations, attackers registered fake computers and their own authenticator apps within hours. Here is the cleanup order that actually locks them out.

When an account gets broken into, the instinct is to reset the password. Do that, but don't stop there. A new report shows why it isn't enough.

Huntress, a security firm, tracked a campaign from July 14 to September 22 that compromised 97 accounts at 79 organizations. The attackers didn't guess passwords. They used a fake sign-in page that passes everything through to the real Microsoft page, then reused the session token Microsoft issued at the end. That token is proof someone already signed in, so nobody gets asked for a code again. We explained this technique here.

What they did in the first hours

A stolen session can expire. So they made sure they wouldn't need it for long.

They added their own sign-in method. In at least 19 organizations, the victim's multi-factor methods were removed and a new one registered within three hours of the first sign-in. In one case, an authenticator app named "iPhone 13" went active less than 51 minutes after the session was stolen.

They added computers. The attackers registered at least 48 fake computers in victims' Microsoft directories. As Huntress put it, a registered device "stays in the directory until someone deletes it."

So a password reset can leave both of those in place.

The cleanup, in order

If you suspect an account is compromised, ask your IT provider to do these together, and in this order:

  1. Revoke every active session for that account, so stolen tokens stop working.
  2. Look at the account's registered sign-in methods and remove any the person doesn't recognize. An unfamiliar phone name is the giveaway.
  3. Check the directory for devices registered recently under that account, and remove the ones nobody can explain.
  4. Reset the password.
  5. Check the inbox rules, because that same campaign hid mail about payroll and deposits.
  6. Review what the account sent and opened while it was compromised, and warn anyone who may have received something from it.

Sessions go first because a stolen session can undo your other steps while you're working. Before any of this is needed, ask your provider how long the first step takes on one account. Ask it now, while nothing is on fire.

What stops it happening again

Regular multi-factor authentication doesn't stop this, because the fake page simply relays the code. Passkeys and Windows Hello do, because they're tied to the real Microsoft address and won't work on a lookalike page. Start with whoever handles money and whoever holds admin rights.

Also ask who is allowed to add devices to your directory. Most small companies have never looked at that setting.

AI-researched from public sources. We label AI-assisted writing — see our trust page.

See your own risk

Want this for your own Microsoft cloud?

Tenant Strike finds the security gaps in your Microsoft 365 and Azure, shows how they chain into a real break-in, and hands you a step-by-step fix for every one — read-only. The scanner never requests a write permission. The optional configuration reader holds one, ConfigurationMonitoring.ReadWrite.All, whose only writes are Microsoft’s own snapshot records; it cannot change your tenant. Start a 7-day Pro trial — no credit card.