FBI Warns Microsoft 365 Users About Device Code Phishing Scams
Published November 16, 2026
The Federal Bureau of Investigation (FBI) has warned Microsoft 365 users about device code phishing scams that allow cybercriminals to hijack accounts without stealing passwords or directly intercepting multi-factor authentication (MFA) codes.
In an official advisory issued on May 21, 2026, the FBI identified Kali365, a phishing-as-a-service platform that exploits Microsoft’s legitimate device authorization process to capture OAuth access and refresh tokens.
The threat remains relevant in November 2026. On November 5, security researchers at Push Security reported phishing campaigns that impersonated technology events associated with OpenAI, SpaceX, and Anthropic to trick employees into approving unauthorized Microsoft account access.
The biggest risk is that victims may be using a genuine Microsoft sign-in page while unknowingly authorizing an attacker-controlled session.
The FBI recommends restricting unnecessary device code authentication, while users should never approve unexpected device authorization requests.
What Did the FBI Warn Microsoft 365 Users About?
The FBI’s warning focuses on a growing phishing technique that abuses the OAuth 2.0 device authorization process used by Microsoft services.
Unlike traditional phishing, which typically involves fraudulent login pages designed to steal passwords, device code phishing manipulates an existing authentication feature.
Microsoft’s device authorization process allows users to sign in on devices that cannot easily display a complete login interface.
For example, a smart TV, printer, or conference room device may display a temporary code. The user enters that code on a separate computer or smartphone to authorize the original device.
Cybercriminals can misuse this functionality by initiating a device authorization request themselves and persuading someone else to complete it.
The FBI specifically identified the Kali365 phishing platform as a major example of this threat.
According to the agency, the service provides capabilities including:
- AI-generated phishing messages designed to impersonate trusted organizations.
- Automated phishing campaign templates.
- Real-time monitoring of targeted accounts.
- OAuth access and refresh token capture.
- Infrastructure that makes sophisticated attacks accessible to less experienced criminals.
Once the attack succeeds, the criminal may gain access to Microsoft 365 services permitted by the compromised account.
That can include business emails, collaboration tools, and cloud documents.
The FBI’s advisory demonstrates why a successful MFA verification does not always guarantee that the correct person or device is receiving account access.
How Does Microsoft 365 Device Code Phishing Work?
A typical device code phishing attack involves four stages.
1. The attacker sends a convincing phishing message
The victim receives an email, Microsoft Teams message, or invitation that appears to come from a legitimate service.
Common scenarios involve shared documents, meeting invitations, business files, invoices, or account verification requests.
The message instructs the recipient to enter a device code to view the requested information.
Because the message often imitates a familiar business process, the victim may assume the request is legitimate.
2. The victim opens a genuine Microsoft login page
The attacker provides a temporary authorization code generated through Microsoft’s legitimate device authentication system.
The victim is directed to Microsoft’s real device sign-in portal, such as microsoft.com/devicelogin.
This is one of the most deceptive elements of the attack.
The authentication website itself may be genuine, even though the request is malicious.
A user who checks only the website address may fail to recognize the scam.
3. The victim authorizes the attacker’s session
After entering the supplied code, the victim may be asked to sign in or approve an authentication request.
If the process succeeds, Microsoft issues authorization tokens associated with the session initiated by the attacker.
The victim believes they are confirming access to a document or service.
In reality, they may be granting access to an unauthorized device or application.
4. The attacker accesses Microsoft 365 resources
The captured authorization can allow the attacker to access Microsoft 365 services within the permissions granted to that session.
Depending on those permissions, attackers may be able to:
- Read Outlook emails and attachments.
- Access files stored in OneDrive.
- Interact with Microsoft Teams or other connected services.
- Collect sensitive company information.
- Attempt to maintain access through additional device registration or account changes.
The attacker may not need the user’s password or another MFA verification while the stolen authorization remains valid.
Microsoft warns that some attackers also create malicious inbox rules or register additional devices to extend their access.
Why Are These Phishing Attacks Difficult to Detect?
Traditional cybersecurity awareness often teaches users to check URLs before entering passwords.
That remains useful advice, but it is not sufficient for device code phishing.
The primary deception is not necessarily a counterfeit Microsoft website. Instead, attackers persuade legitimate users to approve an authorization request they did not initiate.
This creates several security challenges.
Legitimate authentication infrastructure: The victim may complete the process on an official Microsoft website.
No password theft required: In a device code phishing attack, the attacker may obtain OAuth tokens without directly collecting the user’s password.
MFA may already be completed: The victim’s normal authentication method can successfully verify their identity while granting access to the wrong session.
Potential persistence: Attackers may attempt to maintain access through refresh tokens, unauthorized device registration, or additional changes to the account.
Microsoft’s September 22, 2026, investigation into the EvilTokens phishing platform reported the compromise of more than 12,000 inboxes across over 10,000 organizations.
Those figures relate to EvilTokens, not specifically to Kali365, but they illustrate the scale that device code phishing campaigns can reach.
New Phishing Campaigns Target Microsoft Users in November 2026
The FBI’s warning is not an isolated event.
Research published by Push Security on November 5, 2026, revealed a campaign using fake event invitations associated with major technology brands.
Attackers created fraudulent registration pages advertising supposed events and promotional rewards connected with OpenAI, SpaceX, and Anthropic.
Visitors were encouraged to authenticate using corporate accounts.
When a victim selected the Microsoft sign-in option, the page initiated a device code phishing flow through Kali365.
Researchers also identified the use of VoidProxy, an adversary-in-the-middle phishing platform capable of capturing authentication sessions.
The campaign combined trusted brand names, realistic invitation pages, and authentication workflows to make fraudulent sign-ins appear credible.
These findings show that criminals are adapting device code phishing to current technology trends and workplace activities.
Importantly, the impersonated technology companies were used as phishing lures; the research did not establish that those companies operated the fraudulent events.
How Can Microsoft 365 Users Protect Their Accounts?
The most important security rule is simple:
Never enter a device authorization code that you did not request as part of a login or device setup you personally initiated.
Users should also take the following precautions.
Verify unexpected authentication requests
If an email or Teams message asks you to complete a device login, verify the request independently.
Do not rely entirely on the sender’s display name, a familiar company logo, or a legitimate-looking sign-in page.
Contact the person or IT department through an established communication channel.
Review what you are authorizing
Before accepting an authentication request, check the application name and the purpose of the authorization.
If you are not currently connecting a device or application, cancel the request.
Never approve a login merely because someone claims that your Microsoft 365 account requires immediate verification.
Keep multi-factor authentication enabled
MFA remains an important security measure despite these attacks.
It reduces the risk of unauthorized access when passwords are stolen or reused.
However, users should understand the limitations of traditional verification methods.
For more information, read our guide to Microsoft Multi-Factor Authentication.
Consider phishing-resistant authentication
Organizations should adopt phishing-resistant methods, such as FIDO2 security keys or supported passkeys, where practical.
These methods provide stronger protection against fraudulent authentication websites than conventional one-time passwords.
However, phishing-resistant login methods should still be combined with controls that prevent users from authorizing unexpected devices.
Our comparison of Microsoft Authenticator vs Passkeys explains how these authentication methods differ.
What Should You Do if You Entered a Suspicious Device Code?
If you believe you entered an attacker-supplied code on a Microsoft verification page, take action immediately.
First, stop interacting with the suspicious message or website. Do not approve any additional requests.
For a work or school Microsoft 365 account, contact your organization’s IT or security administrator immediately.
Explain that you may have authorized an unfamiliar device through a device code authentication request.
Administrators should investigate the account’s sign-in history, authentication events, connected applications, registered devices, and suspicious account activity.
The response may require:
- Revoking compromised refresh tokens and sign-in sessions.
- Investigating and removing unauthorized device registrations.
- Reviewing application permissions and suspicious inbox rules.
- Temporarily disabling the affected account if immediate containment is necessary.
- Changing the password if there is also evidence that credentials were exposed.
- Monitoring the account for further suspicious activity.
Microsoft notes that existing access tokens may remain usable for a limited period after some session revocation actions.
Changing a password alone may not immediately terminate every attacker-controlled session.
For personal accounts, review available Microsoft account security activity and sign-out controls, and seek official Microsoft account support when necessary.
Affected users in the United States can also report the incident to the FBI’s Internet Crime Complaint Center at IC3.gov.
What Should Businesses Do to Stop Device Code Phishing?
Microsoft 365 administrators have additional controls that can reduce the attack surface.
The FBI recommends auditing legitimate device code authentication activity and restricting or blocking unnecessary device code flows.
Microsoft Entra Conditional Access provides controls that organizations can use to limit device code authentication.
Before blocking these flows, administrators should identify legitimate business dependencies, including conferencing devices or other applications that rely on device authorization.
Organizations should also monitor suspicious OAuth activity, unexpected device registrations, and abnormal sign-in behavior.
Security teams should regularly train employees to recognize phishing messages that involve legitimate Microsoft authentication pages.
This is particularly important for finance, human resources, executives, and employees with access to sensitive business information.
Can an Authenticator App Prevent Device Code Phishing?
An authenticator app can strengthen account security, but its protection depends on the authentication method and attack scenario.
Traditional time-based one-time passwords (TOTP) help protect supported accounts from unauthorized sign-ins involving stolen passwords.
Some authenticator applications and identity platforms also support stronger authentication methods, such as passkeys.
However, a standard authenticator code cannot automatically prevent someone from authorizing an attacker-controlled OAuth device session.
This does not mean users should disable their authenticator applications.
Instead, they should combine strong authentication with careful verification of sign-in requests, account monitoring, and appropriate identity security policies.
The Authenticator App by Begamob can be used to generate verification codes for compatible TOTP-enabled services. It should not be presented as a tool that blocks Microsoft device code phishing or controls Microsoft Entra policies.
Frequently Asked Questions
Is Microsoft 365 device code phishing a real threat?
Yes. The FBI issued an official warning about Kali365 on May 21, 2026, and independent security researchers have continued documenting related attacks throughout the year.
Can hackers bypass Microsoft Authenticator without stealing passwords?
Attackers may obtain valid authorization tokens through device code phishing without directly stealing the user’s password. This does not mean the attacker has broken the authenticator application’s underlying security algorithms.
Is the Microsoft device login website unsafe?
No. Microsoft’s official device authentication service is legitimate. The danger arises when users enter codes supplied by attackers and approve authorization requests they did not initiate.
Should users disable Microsoft 365 MFA?
No. Users should keep MFA enabled and consider phishing-resistant authentication methods where supported. Organizations should also restrict unnecessary device code flows.
Can changing my Microsoft password stop this attack?
Changing a password may help if credentials have been exposed, but it may not immediately invalidate every stolen access token. Users and administrators should also review and revoke unauthorized sessions and devices.
Final Thoughts
The FBI’s warning about Microsoft 365 device code phishing highlights an increasingly important cybersecurity risk: attackers do not always need stolen passwords to compromise online accounts.
By manipulating legitimate authorization workflows, cybercriminals can trick users into granting access to Microsoft 365 resources while making the process appear trustworthy.
The continued appearance of Kali365-related campaigns in November 2026 reinforces the need for stronger identity protection.
For users, the most important precaution is to reject device authorization requests they did not initiate.
For organizations, restricting unnecessary device code authentication, monitoring OAuth token activity, and using phishing-resistant authentication are essential parts of a layered defense strategy.
Sources and References
- FBI Internet Crime Complaint Center — Kali365 Phishing-as-a-Service Kit Hijacks Microsoft 365 Access Tokens — May 21, 2026.
- Microsoft Security Blog — Unmasking EvilTokens: Getting to the Root of Device Code Phishing — September 22, 2026.
- Push Security — Analyzing a Fake Event Campaign Combining AiTM and Device Code Phishing Payloads — November 5, 2026.
- Microsoft Security Blog — Email Threat Landscape: Q3 2026 Trends and Insights — November 5, 2026.