Join our Newsletter — 33% off our NHI Course

Could Kali365 let AiTM phishing bypass Microsoft 365 MFA?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20225
Topic starter  

TL;DR: $250/month shows how Kali365 turns Microsoft 365 sessions into post-login compromise, in Todyl case work. Session governance and behavioural monitoring have to carry more weight when login checks can be satisfied and the attacker still keeps working.

Editorial analysis by NHI Mgmt Group, based on content published by Todyl: “Kali365 PhaaS: Inside the Attack Infrastructure”.

By the numbers:

  • Kali365 was offered at $250/month, paid in Bitcoin, as a subscription phishing service.
  • The infrastructure used port 8443 for operator panel access alongside port 443 for the victim-facing phishing portal.

Key questions

Q: Why do fresh phishing domains evade traditional detection so easily?

A: Because reputation systems depend on prior observation, while disposable infrastructure is designed to move faster than blocklists and vendor feeds.

Q: What are the signs that a mailbox has been abused after login?

A: Watch for forwarding-rule creation, unusual inbox access from a new device or location, bulk contact export, and outbound messages that match the user’s tone but occur immediately after authentication.

Q: What happens when session cookies are stolen during MFA phishing?

A: When session cookies are stolen, the attacker may be able to reuse the authenticated session and access the victim’s account without triggering another MFA challenge.

Practitioner guidance

  • Instrument post-authentication detections Alert on forwarding-rule creation, mass contact export, inbox access from new locations, and privilege discovery immediately after successful sign-in.
  • Constrain token usability Restrict session token use to compliant, managed devices so a stolen token is less useful outside the expected device and network context.
  • Shorten session lifetime and revoke aggressively Reduce the window in which a captured token remains valid, especially for accounts with access to finance, executives, or administrators.

Bottom line: Kali365 shows that MFA can be satisfied and still leave the attacker with a usable Microsoft 365 session.

Glossary terms: Adversary-in-the-middle phishing, Session Token Theft, Post-Authentication Monitoring, Phishing-as-a-service

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20715
 

Session theft has become the real control boundary: This kit shows that successful MFA no longer proves trust in the session that follows. The control failure is not a weak password or a missing second factor, but the assumption that a verified login means the account is safe for the rest of the session. Practitioners should treat token replay, post-authentication mailbox abuse, and forwarding-rule creation as the real risk surface.

A question worth separating out:

Q: How should teams respond when a stolen Microsoft 365 token is suspected?

A: Revoke the session, inspect mailbox rules and recent sends, reset the account, and check whether the same infrastructure touched other users. Then review whether the account was allowed to operate from unmanaged devices, because token replay is far easier when session controls are weak.

👉 Read our full editorial: Kali365 shows how AiTM phishing outpaces MFA controls


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.