Security

Entra ID OAuth Redirect Abuse Fuels Phishing Attacks

3 min read

Summary

Microsoft says attackers are abusing a normal Microsoft Entra ID OAuth redirect behavior to turn trusted login links into phishing or malware delivery paths, often by forcing an OAuth error and sending victims to attacker-controlled redirect URIs. The campaign matters because it can bypass user suspicion and some security filters without stealing tokens, and it has been observed targeting government and public-sector organizations.

Need help with Security?Talk to an Expert

Introduction: why this matters

OAuth links to well-known identity providers (IdPs) like Microsoft Entra ID are often trusted by users and, in some cases, treated more leniently by security controls. Microsoft’s latest research highlights a “by design” OAuth redirection behavior being abused to send users from legitimate login domains to attacker infrastructure—enabling phishing and malware delivery while looking like a normal sign-in flow.

This is particularly relevant for IT admins in government and public-sector organizations, which were specifically targeted in the observed activity.

What’s new / key findings

Microsoft Defender Security Research Team observed phishing-led exploitation of OAuth redirection mechanics across email, identity, and endpoint signals:

  • Abuse of silent OAuth flows: Attackers craft OAuth authorization URLs using parameters like prompt=none to attempt a silent authentication check (no UI).
  • Intentionally invalid scopes to force an error path: Requests include scope=<invalid_scope> (or other failure triggers) to reliably generate an OAuth error.
  • Error-driven redirect to attacker-controlled URI: When the IdP returns an error (for example, interaction_required), the browser is redirected to the app’s registered redirect URI, which the attacker configures to point to phishing pages or malware download sites.
  • No token theft required for the redirect: The attacker is not necessarily trying to complete OAuth successfully; the redirect is the main goal.
  • State parameter misuse for personalization: The state parameter—meant for request/response correlation—was repurposed to pass the victim’s email address (plaintext, hex, Base64, or custom encoding) so phishing pages can auto-populate identifiers.
  • Campaign delivery patterns: Phishing lures included e-signature requests, financial/social security themes, document sharing, Teams/meeting content, and password reset prompts. Some used PDF attachments with embedded links and even .ics calendar invites.
  • Downstream tooling: Post-redirect pages frequently used phishing frameworks like EvilProxy (attacker-in-the-middle) designed to capture credentials and session cookies, sometimes adding CAPTCHA/interstitial steps.

Impact on IT administrators and end users

  • Higher click-through risk: Links begin on trusted IdP domains (for example, login.microsoftonline.com), increasing user confidence.
  • Defense bypass pressure: Traditional URL reputation checks may focus on the initial domain and miss the eventual destination.
  • Visibility needs across layers: Microsoft notes Defender correlated signals across email, identity, and endpoint, emphasizing that single-control detection may be insufficient.
  • Ongoing threat: Microsoft Entra disabled observed malicious OAuth applications, but related activity persists—monitoring is still required.

Action items / next steps

  1. Hunt for suspicious OAuth authorize patterns in logs and proxy telemetry, especially:
    • prompt=none combined with unusual/invalid scope values
    • Frequent OAuth failures followed by redirects to non-corporate domains
    • Use of /common/ in unexpected high-volume phishing contexts
  2. Review and restrict app consent and app registrations:
    • Audit newly created apps and redirect URIs for untrusted domains
    • Tighten who can register applications/modify redirect URIs in Entra ID
  3. Strengthen phishing protections beyond “trusted domain” checks:
    • Ensure URL detonation/safe-link tooling follows redirects
    • Educate users that “starts at Microsoft sign-in” does not guarantee safety
  4. Validate Conditional Access and session controls:
    • Monitor sign-in and OAuth error telemetry for anomalies and targeted user groups
  5. Use Defender correlation:
    • Leverage Microsoft Defender for Office 365 + Defender for Identity/Endpoint to correlate email lure, sign-in behavior, and endpoint payload activity.

Need help with Security?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

OAuthMicrosoft Entra IDphishingMicrosoft Defenderidentity security

Related Posts

Security

Microsoft Sentinel Named a 2026 SIEM Leader

Microsoft has been named a Leader in the 2026 Gartner Magic Quadrant for SIEM, highlighting the continued momentum behind Microsoft Sentinel. The announcement also underscores Microsoft's push toward integrated, AI-powered security operations through deep Sentinel integration with the new Integrated Security Operations Center in Microsoft Defender.

Security

Microsoft Perception GA: Agentic Security at Ignite

Microsoft has made Microsoft Perception generally available, introducing an agentic security platform that coordinates red, blue, and green team agents through automated playbooks. Announced at Ignite 2026, the update also expands Defender and Sentinel capabilities to help security teams detect, investigate, and remediate AI-speed threats while keeping administrators in control.

Security

Device Code Phishing Risks for AI Coding Agents

Microsoft warns that device code phishing can be used against AI coding agents such as GitHub Copilot CLI, not just user mailboxes or cloud apps. In a controlled lab, a single approved device code sign-in could enable remote session steering, memory poisoning, synced session exposure, and private repository access depending on account permissions and enabled features.

Security

Microsoft 365 Outage Phishing Campaign Targets Users

Microsoft Threat Intelligence reported a high-volume phishing campaign that impersonates Microsoft 365 service-health notifications to trick users into clicking malicious links. The campaign matters because it uses outage-themed urgency and recipient-specific tracking to target multiple industries, increasing the risk of credential theft and follow-on account compromise.

Security

SCKit ScreenConnect Attack: MSPs Must Hunt Now

Microsoft Threat Intelligence confirmed a campaign abusing ConnectWise ScreenConnect to deploy unauthorized remote-access clients and the SCKit worm on MSP-managed endpoints. The activity can also target technician sessions, making this a high-priority incident for defenders because removing a rogue client alone does not eliminate persistence or invalidate exposed sessions.

Security

AI Agent Supply Chain Attacks Target Coding Tools

Microsoft Security researchers detailed two post-training supply chain attack paths that can backdoor coding and terminal agents: dataset poisoning and model poisoning. The findings matter because compromised agents can misuse tools, execute commands, and access sensitive environments even when prompts appear benign, reinforcing the need for stronger controls around training data, model provenance, and tool permissions.