OAuth Device Code Phishing Campaigns Use Microsoft Login Flow to Steal Tokens

· Original article ↗

Summary

ANY.RUN analysts report more than 180 URLs in a week abusing Microsoft OAuth device authorization: victims enter attacker-generated codes on legitimate Microsoft pages, granting attackers tokens. The article describes SSL decryption exposing campaign scripts and network

Key points

  • ANY.RUN analysts report detecting more than 180 phishing URLs in one week, including infrastructure on worker[.]dev and related domains.
  • Attackers initiate OAuth device authorization and display a user_code on a phishing page; victims enter it at microsoft[.]com/devicelogin after authenticating on a legitimate Microsoft page.
  • The article says this approval can issue access and refresh tokens to attackers without collecting credentials on a fake login page.
  • The article describes encrypted HTTPS traffic and legitimate Microsoft infrastructure as obstacles for domain- and form-based phishing detection.
  • ANY.RUN says its sandbox can extract TLS keys from process memory to reveal scripts, API requests such as /api/device/start and /api/device/status, and the X-Antibot-Token header.
  • Suggested responses include current threat intelligence, sandbox analysis with SSL decryption, and threat hunting to correlate campaign infrastructure.

Article Details

Topic
Phishing campaigns abuse Microsoft’s OAuth Device Code flow to induce victims to approve attacker-initiated authorizations, enabling token-based Microsoft 365 account takeover. The article describes SSL decryption as a way to expose the campaigns’ encrypted network activity and phishing infrastructure.

Indicators of compromise

TypeIndicatorContext
DOMAINaarathe-ramraj-tipgroup-com-au-s-account[.]workers[.]devListed as phishing infrastructure used by the OAuth Device Code phishing campaign.
DOMAINab-monvoisinproduction-com-s-account[.]workers[.]devListed as phishing infrastructure used by the OAuth Device Code phishing campaign.
DOMAINaiinnovationsfly[.]comListed as phishing infrastructure associated with the campaign.
DOMAINandy-bardigans-com-s-account[.]workers[.]devListed as phishing infrastructure used by the OAuth Device Code phishing campaign.
DOMAINastrolinktech[.]comListed as phishing infrastructure associated with the campaign.
DOMAINdennis-saltertrusss-com-s-account[.]workers[.]devListed as phishing infrastructure used by the OAuth Device Code phishing campaign.
DOMAINdibafef289[.]workers[.]devListed as phishing infrastructure used by the OAuth Device Code phishing campaign.
DOMAINrockymountainhi[.]workers[.]devListed as phishing infrastructure used by the OAuth Device Code phishing campaign.
DOMAINsandra-solorzano-duncanfamilyfarms-net-s-account[.]workers[.]devListed as phishing infrastructure used by the OAuth Device Code phishing campaign.
DOMAINsinger-bodners-bau-at-s-account[.]workers[.]devListed as phishing infrastructure used by the OAuth Device Code phishing campaign.
DOMAINsubzero908[.]workers[.]devListed as phishing infrastructure used by the OAuth Device Code phishing campaign.
DOMAINtyler2miler-proton-me-s-account[.]workers[.]devListed as phishing infrastructure used by the OAuth Device Code phishing campaign.
DOMAINworkspace1717-outlook-com-s-account[.]workers[.]devListed as phishing infrastructure used by the OAuth Device Code phishing campaign.

Vendors

Products

Tools

Countries

Industries

Related Articles