Microsoft Defender for Identity
Identity protection

Alerts Xdr

In brief

The page’s DevRel metadata links were updated, and the “AADInternals private key extraction attempt” alert entry was removed.

What Defender admins need to know

Administrators who use this page as an alert reference should review the updated content.

Summaries are generated from the documentation change itself.

Documentation change

The comparison below shows only the changed extract. Use the full-page view for complete context.

Security alert name Severity MITRE Technique Detector ID
A compromised user account signed in
Description:Credential stuffing led to a successful sign in, confirming an account has been compromised and accessed by an unauthorized party.
High T1078 xdr_CredentialStuffingToolObserved
AADInternals private key extraction attempt
Description:AADInternals was used to decrypt a certificate's private key as an administrator. A successfully decrypted private key might be used to impersonate hybrid components such as Pass-through Authentication (PTA) and Microsoft Entra Cloud Sync, which might lead to lateral movement to the cloud.
HighT1552.004xdr_AADInternalsPrivateKeyExtractAttempt
Anomalous OAuth device code authentication activity
Description:An OAuth device code authentication was detected in a context that deviates from the user’s typical behavior and sign-in patterns. Device code flow is generally associated with command-line tools, IoT devices, or non-browser-based applications. This anomalous activity may indicate a potential device code phishing attack and requires immediate investigation due to the risk of unauthorized token issuance or post-authentication token abuse.
Medium T1528, T1078.004 xdr_AnomalousDeviceCodeAuthV2
Anomalous OAuth device code authentication activity
Description:An OAuth device code authentication was detected in a context that deviates from the user’s typical behavior and sign-in patterns. Device code flow is generally associated with command-line tools, IoT devices, or non-browser-based applications. This anomalous activity may indicate a potential device code phishing attack and requires immediate investigation due to the risk of unauthorized token issuance or post-authentication token abuse.
Medium T1528, T1078.004 xdr_AnomalousDeviceCodeAuthV3
Anomalous token exchange following device code authentication
Description:An OAuth Device Code authentication was detected in an unusual context based on user behavior and sign-in patterns. Due to the design of Device Code flows, this activity requires immediate investigation as it may indicate unauthorized token issuance or post-authentication abuse.
High T1528, T1078.004 xdr_AnomalousDeviceCodeAuth