Huntress Details Phishing Kits That Steal Microsoft 365 Session Tokens

· Original article ↗

Summary

Huntress analyzed EvilTokens, Knight Office and Kali365, phishing kits that capture and replay Microsoft 365 session tokens. The sponsored article explains device-code and AiTM techniques and recommends ways to detect and contain session theft.

Key points

  • Huntress says the three analyzed kits—EvilTokens, Knight Office and Kali365—target Microsoft 365 session tokens.
  • Device-code phishing can capture authorization after victims authenticate with the identity provider.
  • AiTM kits relay authentication in real time and can capture session information even when victims complete MFA.
  • Kali365 reportedly supports device-code flows and reverse-proxy lures, token replay, persistent access and built-in AI features.
  • Defenders are advised to investigate the sequence from phishing lure through authentication, token use, device registration and mailbox activity.
  • Suggested response steps include revoking refresh tokens, removing unauthorized devices and credentials, restricting device-code authentication where possible, and monitoring for replay or re-entry.

Article Details

Defense Focus
Detect and contain Microsoft 365 session-token theft and replay, following the activity from the phishing lure through authentication and token use to device and mailbox activity.
Detection Methods
  • Check for successful sign-ins from unfamiliar cloud infrastructure.
  • Hunt for device code authentication and automated token refresh.
  • Review new device registrations, authentication methods, and mailbox activity.
  • Correlate the sequence from the phishing lure through authentication, token issuance or theft, device registration, and mailbox activity.
  • After containment, monitor for token replay or re-entry, including if the original phishing domain disappears.
Data Sources
  • Successful sign-in and authentication activity
  • Device registration and authentication-method records
  • Mailbox activity, including forwarding rules and outbound phishing
  • Token issuance, refresh, and use activity
Defensive Actions
  • Contain identity artifacts, not only the original phishing lure.
  • Revoke refresh tokens.
  • Remove unauthorized devices and Windows Hello credentials.
  • Restrict or block device code authentication where possible.
  • Investigate mailbox access, forwarding rules, and outbound phishing.
  • Continue hunting for replay or re-entry after containment.

MITRE ATT&CK

Vendors

Products

Related Articles