Microsoft Entra OAuth Client ID Spoofing
Score: 8/10

Microsoft Entra OAuth Client ID Spoofing

Threat actors are spoofing OAuth client IDs in Microsoft Entra to perform stealthy user enumeration and credential validation without generating successful sign-in logs.

Executive Summary

Multiple threat actors, including the campaigns tracked as UNK_pyreq2323 and UNK_OutFlareAZ, are increasingly utilizing OAuth client ID spoofing to bypass traditional identity monitoring in Microsoft Entra environments. By supplying valid-looking but unregistered Application IDs during the Resource Owner Password Credentials (ROPC) flow, attackers can infer the validity of usernames and passwords based on specific Entra error codes.

This technique is particularly dangerous because it results in blank 'Application Name' fields in Entra sign-in logs, effectively evading security detections that rely on application-specific volume surges or Conditional Access policies. Proofpoint observed millions of spoofed IDs targeting over two million users, with some campaigns resulting in significant account lockouts across thousands of organizations. This represents a mature shift in cloud-based reconnaissance tradecraft designed to identify valid credentials before attempting an actual login.

Key Details

Threat Name

Microsoft Entra OAuth Client ID Spoofing

Affects

—

Adversary

UNK_pyreq2323 Other Adversaries and Aliases: UNK_OutFlareAZ

Malware/Tools

Invoke-ClientIdSpoofEnum

Report Score

8out of 10
Quality Score
Good
IOC Quality6
TTP Details9
Detection Guidance7
Enterprise Relevance10
Clarity & Structure9
Technical Depth8

Sources