MFASweep is a PowerShell script that attempts to log in to various Microsoft services using a provided set of credentials and will attempt to identify if MFA is enabled. Depending on how conditional access policies and other multi-factor authentication settings are configured some protocols may end up being left single factor. It also has an additional check for ADFS configurations and can attempt to log in to the on-prem ADFS server if detected.
Currently MFASweep has the ability to login to the following services:
- Microsoft Graph API
- Azure Service Management API
- Microsoft 365 Exchange Web Services
- Microsoft 365 Web Portal w/ 6 device types (Windows, Linux, MacOS, Android Phone, iPhone, Windows Phone)
- Microsoft 365 Active Sync
- ADFS
WARNING: This script attempts to login to the provided account TEN (10) different times (11 if you include ADFS). If you entered an incorrect password this may lock the account out.
For more information check out the blog post here: Exploiting MFA Inconsistencies on Microsoft Services
This command will use the provided credentials and attempt to authenticate to the Microsoft Graph API, Azure Service Management API, Microsoft 365 Exchange Web Services, Microsoft 365 Web Portal with both a desktop browser and mobile, and Microsoft 365 Active Sync. If any authentication methods result in success, tokens and/or cookies will be written to AccessTokens.json. (Currently does not log cookies or tokens for EWS, ActiveSync, and ADFS)
Invoke-MFASweep -Username targetuser@targetdomain.com -Password Winter2024 -WriteTokensKey optional switches:
-WriteTokens– saves any collected access/refresh tokens and cookies toAccessTokens.json.-Recon/-IncludeADFS– enumerate ADFS settings and test the detected on-prem ADFS endpoint.-UseChromium– forces Microsoft 365 web portal checks through a Playwright-driven Chromium instance to better mimic real browsers (see below for setup steps).
This command runs with the default auth methods and checks for ADFS as well.
Invoke-MFASweep -Username targetuser@targetdomain.com -Password Winter2020 -Recon -IncludeADFSMicrosoft now blocks many scripted requests to the Microsoft 365 web portal. MFASweep can optionally emulate a real browser session by calling Playwright/Chromium.
- Install Node.js (v18+ recommended).
- From the repository root run:
npm install
npx playwright install chromium- Execute MFASweep with the
-UseChromiumswitch (other parameters remain the same):
Invoke-MFASweep -Username targetuser@targetdomain.com -Password Winter2024 -UseChromium -WriteTokensDuring Chromium mode the script launches a headless browser for every user agent check, captures cookies/tokens, and reports whether MFA was required.
Each individual module can be run separately if needed as well.
Microsoft Graph API
Invoke-GraphAPIAuth -Username targetuser@targetdomain.com -Password Winter2020Azure Service Management API
Invoke-AzureManagementAPIAuth -Username targetuser@targetdomain.com -Password Winter2020Microsoft 365 Exchange Web Services
Invoke-EWSAuth -Username targetuser@targetdomain.com -Password Winter2020Microsoft 365 Web Portal
Invoke-O365WebPortalAuth -Username targetuser@targetdomain.com -Password Winter2020Microsoft 365 Web Portal w/ Mobile User Agent
Invoke-O365WebPortalAuthMobile -Username targetuser@targetdomain.com -Password Winter2020Microsoft 365 Active Sync
Invoke-O365ActiveSyncAuth -Username targetuser@targetdomain.com -Password Winter2020ADFS
Invoke-ADFSAuth -Username targetuser@targetdomain.com -Password Winter2020The Invoke-BruteClientIDs function will loop through various resource types and client IDs during ROPC auth to find single factor access for various combinations of client IDs and resources. If any authentication methods result in success, tokens and/or cookies will be written to AccessTokens.json. (Currently does not log cookies or tokens for EWS, ActiveSync, and ADFS)
Invoke-BruteClientIDs -Username targetuser@targetdomain.com -Password Winter2024 -VerboseOut