Accounts & identity
MFA bypass
MFA bypass
MFA bypass abuses implementation weaknesses, recovery paths or stolen sessions to gain access without meeting the intended protection.
Fiche de sensibilisationPrête à diffuser à vos équipes ou clients
MIGHT YOU BE AFFECTED?
Turn knowledge into action.
How does this work?
MFA adds an extra proof at sign-in, but shared codes, mistakenly approved prompts and previously authenticated sessions can be abused. Weak recovery procedures or uncontrolled enrollment of new factors also create exposure. Origin-bound passkeys and FIDO2 keys strengthen phishing resistance, although endpoint compromise remains possible.
REAL-WORLD EXAMPLE
« An employee receives a call from a fake support technician requesting a sign-in code. After it is shared, an unknown device appears among the account's security methods. »
Typical sequence
- 1Find a sign-in or recovery path with weaker controls.
- 2Abuse an existing session, relay or implementation weakness.
- 3Obtain authenticated context without the expected MFA challenge.
- 4Reach resources authorised by that context.
- 5Attempt to retain obtained tokens or access.
Warning signs
- Unexpected MFA prompts or codes requested by another person.
- New MFA methods or unknown devices.
- Successful sign-ins after repeated rejected prompts.
- Unusual changes to recovery information.
- Cloud activity without a recent interactive sign-in.
How to protect yourself
- Harden recovery methods and use phishing-resistant MFA to prevent bypass.
- Prefer phishing-resistant passkeys or FIDO2 security keys.
- Use number matching and anti-prompt-fatigue controls when applicable.
- Strongly verify account recovery requests.
- Alert on MFA method enrollment and removal.
- Limit session lifetime and apply conditional access.
- Teach users never to disclose sign-in codes.
If you think you are affected
Stop suspicious activity, preserve relevant logs and messages, revoke affected sessions or credentials, investigate changes and report confirmed exposure to the appropriate team.
Last updated: 8 October 2026