Colour theme
Book a consultation

How phishing sites steal a signed-in session

Understand how phishing can relay an MFA sign-in, then review authentication, session controls and the steps to take after a suspicious login.

An illustration of a hooded figure in a white mask behind a laptop showing a sign-in form.

A sign-in page can show familiar branding and a working multi-factor authentication (MFA) prompt while sitting on an attacker’s website. If you enter a password and approve the request, the attacker may capture the session created by that sign-in.

This is an adversary-in-the-middle attack, often shortened to AiTM. It changes what staff need to check and what IT needs to enforce. Seeing an MFA prompt doesn’t mean the page is safe.

How the sign-in is relayed

The Canadian Centre for Cyber Security’s AiTM guidance describes phishing infrastructure that passes a sign-in between the victim and the real service. The victim completes authentication through that intermediary, which can capture credentials and session material.

To the person signing in, the page looks and behaves like the real one. The web address is often the only visible clue, and it’s easy to miss on a phone or in a hurry. Teach staff to check the domain before they type a password, especially after following a link from an email or shared document.

A session lets an application remember that you’ve signed in. Stolen session material may let an attacker act as you without repeating the same password and MFA checks. What works depends on the application, token lifetime and access controls; a stolen cookie doesn’t guarantee access to every service.

Choose authentication that resists the relay

Passkeys and FIDO2 security keys use authentication tied to the legitimate service. They resist this phishing technique in a way that typed codes and ordinary approval prompts don’t. Number matching helps with unwanted push approvals, but it isn’t phishing-resistant authentication.

Keep MFA enabled while planning an upgrade. Have IT confirm which methods are allowed for each staff group and which are required for sensitive applications. Registering a stronger method won’t protect a sign-in that can still use a weaker alternative.

Our passkey rollout guide covers piloting, recovery and enforcement.

Check session controls separately

Phishing-resistant sign-in doesn’t fix malware on a device or every other way a session can be stolen. Keep browsers and computers supported and patched, and review the applications allowed to access business data.

Microsoft’s token-protection documentation describes binding supported sign-in tokens to a device. Its coverage depends on the application, platform and configuration. Don’t assume enabling it protects every browser session or every cloud service.

Ask IT to try device and session policies on a pilot group first. Record unsupported workflows and exceptions. Then check which applications the policy covers in practice, since its name in the admin console won’t tell you.

Watch activity after the sign-in

A successful login can be part of a compromise. Review unexpected authentication-method changes, mailbox forwarding, app consent and file access alongside sign-in records. Investigate alerts in context, including whether the staff member recognizes the activity.

Make the reporting route easy to find. Staff should contact IT if they signed in from an unexpected document link, approved an unexplained MFA request or noticed a new account setting. They don’t need to prove that an attack occurred before reporting it.

Respond beyond a password reset

If a sign-in may have been intercepted, stop using that page and contact IT through a known channel. Preserve the message, address and approximate time without forwarding the live link around the team.

Have IT contain the account and revoke sessions in the affected services. Microsoft explains that an application can issue its own session, which Entra can’t directly revoke. Password changes and central session revocation therefore need application-specific follow-up.

Check for changed recovery methods, forwarding rules, grants and data access. Our email recovery checklist covers that investigation in more detail.


Featured Image Credit