Skip to main content
Back
IntrusionMicrosoft Entra · SaaS
4 min read

UTA0355 authorization code phishing with fake security conference invitations

Victim
An unnamed user of a Volexity customer
When
October 2025, day not statedDisclosed Dec 4, 2025
Entry
A Microsoft authorization code that the victim sent back after a trusted contact's conference registration lure.

Per Volexity, in October 2025 two compromised WhatsApp identities and a correspondent's compromised email account continued a real thread about a European security conference, then sent the victim a registration link. The link opened Microsoft's own sign-in page for a Microsoft first-party client and the Device Registration Service; the victim signed in and sent back the address that held the authorization code, and how the actor redeemed it is not stated. The actor then read a wide variety of files with the victim's account and created a new device in Microsoft Entra ID with the same name as one of the victim's devices.

What happened

External Parties
Compromised contacts
Volexity
Internet
Microsoft Entra IDissues the code on Microsoft's own page
Microsoft 365 Tenant
Targeted user
Look-alike device
Files of the account

Replaying the UTA0355 October 2025 intrusion

  1. 1

    A trusted thread

    Oct 2025, day not stated

    Two compromised WhatsApp identities and a correspondent's compromised email account continue a real thread about a European security conference, then send the victim a registration link.

  2. 2

    The code handed back

    Oct 2025, day not stated

    The victim signs in on Microsoft's own page for a Microsoft first-party client and sends back the address that holds the authorization code; how the actor redeems it is not stated.

  3. 3

    A look-alike device and the files

    Oct 2025, day not stated

    With the victim's account, the actor creates a new device in Microsoft Entra ID named like one of the victim's devices, and reads a wide variety of files.

Impact

The actor read a wide variety of files from the victim's account and kept access through a device it created in Microsoft Entra ID; the count and kind of files are not stated.

Outcome

Where Microsoft Entra controls fit

Closing device registration and join to all but the administrators who enroll devices would have bounded who could add the look-alike device, though the sources do not say whether the victim's account was outside that group. A Conditional Access policy that requires a compliant device, and the SharePoint and OneDrive block on unmanaged devices where the files sat there, would have capped what a device the actor created could read. The lure and the victim's own sign-in on Microsoft's real page sit outside every cloud control. Check who in your tenant may register or join devices.

Could this have been prevented?

In hindsight, no control would have stopped it. 3 controls would have limited how far it went. 2 steps have no cloud-provider control. The counts below are control assessments, not attack stages: several can address the same step. The same replay with the controls in place before the incident shows where each phase would have been refused or bounded.

0
Prevented
3
Contained
2
Not covered

How it could have been prevented

The same replay with the controls in place. Green marks where a step is refused, blue where it is bounded, and red where no control reaches it. Open a row to read the control, why it acts, and its caveat.

External Parties
Compromised contacts
Volexity
Internet
Microsoft Entra IDissues the code on Microsoft's own page
Microsoft 365 Tenant
Targeted user
Look-alike device
Files of the account

Replaying the UTA0355 October 2025 intrusion

1 · A trusted thread

1 Not covered

2 · The code handed back

1 Not covered

3 · A look-alike device and the files

3 Contained

Key facts

  • Volexity attributed the activity to UTA0355, an actor it assesses as Russian and first reported on in April 2025
  • In October 2025, day not stated, a user's Microsoft 365 account was identified as compromised after anomalous login activity was detected
  • The lure came from two compromised WhatsApp identities and a correspondent's compromised email account, continuing a real thread about a European security conference; the first messages carried no malicious content
  • The link opened Microsoft's own sign-in page and the victim was asked to send back the code Microsoft generated; the report does not say how the code was redeemed or which tokens the actor obtained
  • Volexity's April 2025 report and Elastic's research identify the requested resource as the Device Registration Service
  • The actor accessed a wide variety of files and created a new device in Microsoft Entra ID named like an existing device of the victim; the service and the files are not named

Sources

Every fact in this breakdown comes from the public reporting below. The replay is a model of that reporting, not a reconstruction of the environment it describes.

  1. 1.
    Dangerous Invitations: Russian Threat Actor Spoofs European Security Events in Targeted Phishing AttacksVolexity · Dec 4, 2025 · ResearchLure and rapport building, the authorization code handover, file access, Entra device registration, follow-on campaigns, attribution to UTA0355
  2. 2.
    Phishing for Codes: Russian Threat Actors Target Microsoft 365 OAuth WorkflowsVolexity · Apr 22, 2025 · ResearchThe meaning of the requested resource (Device Registration Service), the earlier use of the same technique, Volexity's recommended controls
  3. 3.
    Entra ID OAuth Phishing DetectionElastic Security Labs · Jun 25, 2025 · ResearchThe identity of the client (Microsoft Authentication Broker) and the resource (Device Registration Service), the technique from code to device registration

The estate in the replay is illustrative and drawn at the level of attack stages; the victim's real environment is not public. Verdicts describe what a control does when it is in place before the incident. They are not an assessment of the victim's security program.

More cloud attack breakdowns

All breakdowns