Russian Actors Abuse Microsoft 365 OAuth Workflows to Phish Accounts

· Original article ↗

Summary

Volexity describes campaigns by suspected Russian actors UTA0352 and UTA0355 that use targeted social engineering and legitimate Microsoft OAuth workflows to steal authorization codes and access victims’ Microsoft 365 accounts.

Key points

  • Since March 2025, UTA0352 and UTA0355 have targeted NGOs, human-rights groups, and people connected to Ukraine using impersonation and one-on-one social engineering via email, Signal, and WhatsApp.
  • Victims are directed to legitimate Microsoft login pages and tricked into sharing an OAuth authorization code or the redirected URL, enabling attackers to obtain access tokens.
  • UTA0352 abused Microsoft first-party OAuth workflows, including Visual Studio Code redirects, to obtain codes with access to victims’ Microsoft 365 resources.
  • UTA0355 used a compromised Ukrainian government email account and targeted the Device Registration Service to add an attacker-controlled device to victims’ Entra ID.
  • Volexity observed UTA0355 subsequently persuading a victim to approve a two-factor authentication request, then downloading the victim’s email using the newly registered device.
  • Recommended defenses include verifying unexpected contacts out of band, monitoring OAuth and device-registration activity, and considering conditional access restrictions for unmanaged devices.

Article Details

Attack Vectors
  • Targeted social engineering via Signal, WhatsApp, and email, using invitations to Ukraine-related video conferences and impersonated European officials.
  • OAuth phishing through legitimate Microsoft 365 authentication workflows, persuading victims to return an authorization code or the redirected URL containing it.
  • UTA0355 used a stolen OAuth authorization code to register a device in the victim’s Microsoft Entra ID, then socially engineered approval of a two-factor authentication request to access email.
Defensive Notes
  • Alert on Microsoft 365 login activity using client_id aebc6443-996d-45c2-90f0-388ff96faa56 with a Microsoft Graph resource, and on the described OAuth URL patterns using insiders.vscode.dev/redirect or vscode-redirect.azurewebsites.net.
  • Consider the business impact of blocking insiders.vscode.dev and vscode-redirect.azurewebsites.net.
  • Train users to verify unexpected contacts out-of-band and never share authorization codes or URLs from browser address bars.
  • Monitor for newly registered devices and correlate registration IP addresses with low-reputation or proxy IP addresses; track subsequent activity using the registered deviceId.
  • Consider conditional access policies that restrict organizational resources to approved or managed devices.
  • Account for the article’s observation that ongoing Microsoft Graph email access may show a Microsoft IP address rather than the attacker’s IP in ClientIPAddress.

MITRE ATT&CK

Threat Actors

Vendors

Products

Tools

Countries

Industries

Related Articles