Skip to content
Home » Articles » Preventing MFA Fatigue and Session Hijacking

Preventing MFA Fatigue and Session Hijacking

The Anatomy of Modern Phishing and Session Hijacking

Modern credential theft has evolved beyond simple password capture. Adversaries now leverage sophisticated adversary-in-the-middle (AiTM) phishing kits, such as Evilginx, to bypass multi-factor authentication (MFA) and hijack active user sessions. These kits operate as reverse proxies, sitting between the victim and legitimate login pages. When a user navigates to a malicious link, the AiTM proxy intercepts their credentials and, crucially, their active session cookies.

This technique is effective because it circumvents traditional MFA challenges. The user completes the MFA prompt on what they believe is the legitimate service, but the AiTM proxy captures the resulting valid session token. With this token, attackers can authenticate to cloud services (e.g., Microsoft 365, Google Workspace) without needing the user’s password or MFA again, until the session token expires or is revoked. This leads to “MFA fatigue,” where users are bombarded with authentication prompts, eventually approving a malicious one out of habit or frustration. The primary goal for attackers is not just credentials, but the session itself.

The 15-Minute First-Responder Runbook: Session Hijacking Triage

When an employee reports clicking a malicious link or suspects their account is compromised, immediate, decisive action is critical. This runbook outlines a rapid response strategy for IT administrators and security analysts.

T+0 to T+2m: Initial Verification and Network Disconnect

  1. Verify Incident Report: Confirm the user’s suspicion. Ask for details: the link clicked, any unusual behaviour, or unexpected MFA prompts.
  2. Immediate Network Disconnect: Instruct the user to physically disconnect their workstation from the network (unplug Ethernet, disable Wi-Fi). This isolates the endpoint, preventing further lateral movement or data exfiltration.
  3. Collect Initial Indicators: If possible and safe, capture the malicious URL, sender details, and any associated IP addresses from email headers or browser history before full isolation.

T+2 to T+5m: Emergency Session Token Invalidation and Password Reset

  1. Invalidate All User Sessions: This is paramount. Revoke all active session tokens for the compromised user across all services, especially cloud identity providers like Entra ID (Azure AD).
# Connect to Microsoft Graph
Connect-MgGraph -Scopes "User.ReadWrite.All", "Directory.ReadWrite.All"

# Specify the UserPrincipalName (UPN) of the compromised user
$userUPN = "compromised.user@yourdomain.com"

# Revoke all active sessions for the specified user
Revoke-MgUserSignAndSession -UserId (Get-MgUser -Filter "UserPrincipalName eq '$userUPN'").Id
  1. Enforce Emergency Password Reset: Force a password reset for the user. Ensure the new password meets strong complexity requirements and is unique.
# Specify the UserPrincipalName (UPN) of the compromised user
$userUPN = "compromised.user@yourdomain.com"

# Generate a secure random password (ensure this is communicated securely to the user)
$newPassword = ConvertTo-SecureString -String (([char[]]([char]48..57 + [char]65..90 + [char]97..122 | Get-Random -Count 16) -join '') + '!@#$%^&*'[Get-Random -Maximum 8]) -AsPlainText -Force

# Reset the user's password in Entra ID
Update-MgUser -UserId (Get-MgUser -Filter "UserPrincipalName eq '$userUPN'").Id -PasswordProfile @{ ForceChangePasswordNextSignIn = $true; Password = $newPassword }
  1. Temporary Account Lockout: As a precautionary measure, consider a temporary account lockout to prevent any immediate re-authentication attempts by the attacker.
# Lock the user account in Entra ID (adjust as needed for on-prem AD)
# Note: Entra ID does not have a direct 'lockout' property like on-prem AD.
# Instead, you can temporarily disable the account and re-enable it.
$userUPN = "compromised.user@yourdomain.com"
Update-MgUser -UserId (Get-MgUser -Filter "UserPrincipalName eq '$userUPN'").Id -AccountEnabled:$false

T+5 to T+10m: Endpoint Quarantine and Persistence Sweep

  1. Endpoint Quarantine: Place the compromised workstation into a dedicated network quarantine segment or VLAN that allows only security tool access. This prevents it from interacting with the production network.
  2. Sweep for Persistence Mechanisms:
    • Mailbox Rules: Check the user’s mailbox for malicious forwarding rules created by the attacker to exfiltrate emails.
# Connect to Exchange Online PowerShell (if not already connected)
# Install-Module -Name ExchangeOnlineManagement
# Connect-ExchangeOnline -UserPrincipalName admin@yourdomain.com

# Get all inbox rules for the compromised user
Get-InboxRule -Mailbox "compromised.user@yourdomain.com" | Format-Table Name, Description, Enabled

# Remove a specific malicious inbox rule (replace "Malicious Rule Name" with actual name)
# Remove-InboxRule -Mailbox "compromised.user@yourdomain.com" -Identity "Malicious Rule Name" -Confirm:$false
*   **OAuth Application Grants:** Review third-party applications granted access to the user's cloud accounts (e.g., Microsoft 365, Google Workspace). Revoke any suspicious or unauthorized grants.
*   **Scheduled Tasks/Registry Run Keys:** On the isolated endpoint, perform a quick scan for newly created scheduled tasks or registry run keys that could establish persistence.

T+10 to T+15m: Incident Documentation, Escalation, and Log Review

  1. Document Everything: Record all actions taken, timestamps, observed indicators, and communication with the user. This forms the basis of the incident report.
  2. Escalate Incident: Inform relevant stakeholders (e.g., CISO, legal, privacy officer) according to your organization’s incident response plan.
  3. Review Sign-in Logs: Analyze sign-in logs for the compromised user in your identity provider (e.g., Entra ID, Okta) for anomalous activity:
    • Unusual geographic locations.
    • Sign-ins from unknown IP addresses or devices.
    • Rapid succession of sign-ins from different locations (“impossible travel”).
    • Attempts to access sensitive resources.

Defensive Identity Hardening

Proactive measures are essential to minimize the impact of MFA fatigue and session hijacking:

  • Phishing-Resistant MFA: Implement FIDO2 security keys (e.g., YubiKeys, Google Titan Keys) or Windows Hello for Business. These methods cryptographically bind authentication to the legitimate site, making AiTM phishing ineffective.
  • Conditional Access Policies: Utilize Entra ID Conditional Access to enforce strict authentication strengths. For example, mandate phishing-resistant MFA for access to sensitive applications or from untrusted networks.
  • Continuous Access Evaluation (CAE): Enable CAE in Entra ID to revoke access tokens immediately upon changes in user conditions (e.g., password reset, account disablement, location change). This significantly reduces the window of opportunity for hijacked sessions.
  • User Training and Simulation: Regularly educate users on the evolving tactics of phishing, including AiTM and MFA fatigue. Conduct simulated phishing campaigns to test and reinforce awareness.
  • Disable Legacy Authentication: Block legacy authentication protocols (e.g., POP3, IMAP, SMTP AUTH) that do not support modern MFA, as these are often targeted for initial access.
  • Review OAuth App Permissions: Regularly audit and prune permissions granted to third-party OAuth applications within your cloud tenants to prevent illicit consent grant attacks.

Need Urgent IT Assistance or Perimeter Defense?

Is your organization vulnerable to active edge exploits, credential harvesting, or compliance audit penalties? Helpdesk.ca provides 24/7/365 managed IT support, emergency incident triage, and co-managed IT escalation for Canadian enterprises.


CANADIAN INCIDENT RESPONSE & MANAGED CYBER DEFENSE

Is Your Organization Prepared to Contain an Active Breach in Under 15 Minutes?

Helpdesk.ca delivers 24/7/365 proactive IT help desk operations, rapid incident triage, and enterprise Microsoft 365 identity hardening for Canadian organizations. Neutralize credential threats before adversaries establish persistence.

Sources & References

Helpdesk.ca Assistant

Please enter your details to start chatting.

Hello! How can I help you today?