M365 Potential AiTM UserLoggedIn via Office App (Tycoon2FA)
Description
Detects Microsoft 365 audit "UserLoggedIn" events consistent with Tycoon 2FA phishing-as-a-service (PhaaS) adversary-in-the-middle (AiTM) activity: the Microsoft Authentication Broker requesting access where the object identifier matches Microsoft Graph or Exchange Online, or the Office web client application authenticating to itself, combined with Node.js-style user agents (node, axios, undici). Tycoon 2FA bypasses MFA by relaying authentication and capturing session material, often targeting Microsoft 365 and Gmail. Baseline legitimate automation and developer tooling before tuning.
Query · kuery
data_stream.dataset:"o365.audit" and event.category:"authentication" and event.action:"UserLoggedIn" and
(
(
o365.audit.ApplicationId:"29d9ed98-a469-4536-ade2-f981bc1d605e" and
o365.audit.ObjectId:(
"00000002-0000-0ff1-ce00-000000000000" or "00000003-0000-0000-c000-000000000000"
)
) or
(
o365.audit.ApplicationId:"4765445b-32c6-49b0-83e6-1d93765276ca" and
o365.audit.ObjectId:"4765445b-32c6-49b0-83e6-1d93765276ca"
)
) and user_agent.original:(node or axios* or undici)
Investigation fields
Pivot points the source recommends for triage.
@timestampo365.audit.UserIduser_agent.originalsource.ipo365.audit.ActorIpAddresssource.geo.country_nameevent.outcomeo365.audit.ApplicationIdo365.audit.ObjectIdo365.audit.ExtendedProperties.RequestTypeevent.provider
Known false positives
- Legitimate Node.js or undici-based automation, health checks, or internal services that use the Microsoft Authentication Broker or the same first-party application IDs against Graph or Exchange may match. Developers using axios or undici with delegated flows can also resemble this pattern.
Analyst notes
Investigating M365 Potential AiTM UserLoggedIn via Office App (Tycoon2FA)
Review o365.audit.UserId, user_agent.original, source.ip or o365.audit.ActorIpAddress, and related Entra ID
sign-in logs (azure.signinlogs) for the same session or time window.
Confirm whether the account owner intentionally authenticated and whether Node.js-style user agents (node, axios, undici) are expected for Microsoft Authentication Broker or Office web client flows in your environment.
Possible investigation steps
- Correlate with
azure.signinlogsfor matching user principal name, IP, and session identifiers. - Review Microsoft Graph or Exchange audit activity following the login for mailbox or data access anomalies.
- Hunt for other
UserLoggedInevents from the same source with unusual user agents or rapid OAuth patterns.
Response and remediation
- If malicious, revoke refresh tokens for the user, reset credentials per policy, and review conditional access outcomes.
- Block or monitor the source IP and escalate per incident procedures.