its a DNS hijack, redirecting connection to a registered domain, the page is a spoof of the workflow,with mitigation vs the MFA by abusing OAuth.
the page is HTTPS, an OAuth token is issued to the malignant client.
there is probably some WPAD malarchy in cases.
the entire workflow has minor variations but once an attacker has access to your M365 the chance of having everything you have done with M365 is very likely.
its not exactly MITM its more like Man Offside of the Middle
what happens next depends on the attackers objective.
It's in the article.. they hijacked the DNS to send the users to an alt phishing website.. looked identical to the Entra (M365) flow.. but the victims were sending their data/secrets/TOTP to hackers on slightly different URLs.
Most people are so used to the login flow, they don't inspect the URLS if the page looks right. Some popups even obscure the URL (almost impossible to detect).
How does MITM work without installing a cert on the victim's machine?
its a DNS hijack, redirecting connection to a registered domain, the page is a spoof of the workflow,with mitigation vs the MFA by abusing OAuth.
the page is HTTPS, an OAuth token is issued to the malignant client.
there is probably some WPAD malarchy in cases.
the entire workflow has minor variations but once an attacker has access to your M365 the chance of having everything you have done with M365 is very likely.
its not exactly MITM its more like Man Offside of the Middle
what happens next depends on the attackers objective.
But what about HSTS and HSTS preloading? This sounds more like a deauth/captive portal phish to me.
It's in the article.. they hijacked the DNS to send the users to an alt phishing website.. looked identical to the Entra (M365) flow.. but the victims were sending their data/secrets/TOTP to hackers on slightly different URLs.
Most people are so used to the login flow, they don't inspect the URLS if the page looks right. Some popups even obscure the URL (almost impossible to detect).