Suspicious M365 Legacy Authentication via BAV2ROPC Client via m365

PremiumReviewedSigma · High · v1
Product
m365
Service
signinlogs
Author
HuntRule
Published
2026-07-19
Updated
2026-08-28

ATT&CK techniques

Initial Access → Lateral Movement
  1. Recon

  2. Resource Dev

  3. Execution

  4. Cred Access

  5. Discovery

  6. Collection

  7. C2

  8. Exfiltration

  9. Impact

What it detects

This rule detects non-interactive Microsoft 365 sign-ins using the BAV2ROPC legacy authentication client. In the Railway PaaS token replay campaign, operators used BAV2ROPC to silently refresh stolen tokens and access mailboxes without triggering interactive MFA, so this client string on sign-ins indicates likely token abuse and legacy protocol exploitation.

Related detections9 linkedT1550.001 — drag to rearrange
Suspicious AWS Federated Console Login From Programmatic Credentials
Suspicious AWS STS Session Token and Role Chaining Abuse via CloudTrail (via aws)
Suspicious AWS GetFederationToken Console Access by JavaGhost (via cloudtrail)
Suspicious AWS STS Role Chaining From Temporary Session Credentials (via cloudtrail)
Suspicious Kubernetes Service Account Token Generation via kubectl
Possible Credential Stuffing Blocked by Conditional Access in Microsoft 365
Suspicious browsercore Execution from Anomalous Parent for PRT Cookie (via process_creation)
Suspicious AWS SSO Account Role Enumeration via ListAccountRoles (via cloudtrail)
Suspicious SES Account Sending Enablement and Identity Verification via CloudTrail
Suspicious M365 Legacy Authentication via BAV2ROPC Client via m365
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.