Suspicious Device Registration Following OAuth Token Theft

PremiumReviewedSigma · Medium · v1
Product
azure
Service
auditlogs
Author
HuntRule
Published
2026-08-04
Updated
2026-08-28

ATT&CK techniques

Persistence → Lateral Movement
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Cred Access

  6. Discovery

  7. Collection

  8. C2

  9. Exfiltration

  10. Impact

What it detects

This rule detects Entra ID device registration and Primary Refresh Token acquisition activity consistent with the ROADtools tradecraft used after OAuth phishing. Registering an attacker-controlled device lets the adversary obtain a PRT and maintain durable access to the tenant beyond the stolen refresh token.

Related detections9 linkedT1550.001 — drag to rearrange
Suspicious Federated Identity Credential On-Behalf-Of Token Flow via Sign-In Logs
Suspicious Salesforce Bulk API Export via aiohttp User Agent
Possible Rogue Device Registration in Entra ID (via azure)
Suspicious Token Request Using Microsoft Authentication Broker Client to Obtain Primary Refresh Token (via azure)
Suspicious Entra Sign-In With Axios Automation User-Agent via AiTM Token Replay (via azure)
Suspicious Azure Tenant Root Elevation via elevateAccess
Malicious Azure AD Token Abuse via Roadtx
Suspicious M365 Sign-In from Synthetic iPhone User Agent via m365
Possible Illicit Consent Grant to OAuth Application via Azure AD
Suspicious Device Registration Following OAuth Token Theft
Pivot detection · T1550.001 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.