t1621-multi-factor-authentication-request-generation

name	T1621_multi-factor-authentication-request-generation
description	Adversaries may attempt to bypass multi-factor authentication (MFA) mechanisms and gain access to accounts by generating MFA requests sent to users.
category	authentication
version	18.1
author	cyberstrike-official
tags	["mitre-attack","enterprise","t1621","credential-access","windows","linux","macos","iaas","saas","office-suite","identity-provider"]
technique_id	T1621
tactic	credential-access
all_tactics	["credential-access"]
platforms	["Windows","Linux","macOS","IaaS","SaaS","Office Suite","Identity Provider"]
mitre_url	https://attack.mitre.org/techniques/T1621
tech_stack	["windows","linux","macos","cloud","saas","office","identity"]
cwe_ids	["CWE-522"]
chains_with	[]
prerequisites	[]
severity_boost	{}

T1621 Multi-Factor Authentication Request Generation

High-Level Description

Adversaries may attempt to bypass multi-factor authentication (MFA) mechanisms and gain access to accounts by generating MFA requests sent to users.

Adversaries in possession of credentials to Valid Accounts may be unable to complete the login process if they lack access to the 2FA or MFA mechanisms required as an additional credential and security control. To circumvent this, adversaries may abuse the automatic generation of push notifications to MFA services such as Duo Push, Microsoft Authenticator, Okta, or similar services to have the user grant access to their account. If adversaries lack credentials to victim accounts, they may also abuse automatic push notification generation when this option is configured for self-service password reset (SSPR).

In some cases, adversaries may continuously repeat login attempts in order to bombard users with MFA push notifications, SMS messages, and phone calls, potentially resulting in the user finally accepting the authentication request in response to “MFA fatigue.”

Kill Chain Phase

• Credential Access (TA0006)

Platforms: Windows, Linux, macOS, IaaS, SaaS, Office Suite, Identity Provider

What to Check

• Identify if Multi-Factor Authentication Request Generation technique is applicable to target environment
• Check Windows systems for indicators of Multi-Factor Authentication Request Generation
• Check Linux systems for indicators of Multi-Factor Authentication Request Generation
• Check macOS systems for indicators of Multi-Factor Authentication Request Generation
• Verify mitigations are bypassed or absent (3 known mitigations)
• Assess detection coverage (1 detection strategies)

How to Test

Manual Testing

1. Identify Attack Surface: Determine if the target environment is susceptible to Multi-Factor Authentication Request Generation by examining the target platforms (Windows, Linux, macOS).

2. Assess Existing Defenses: Review whether mitigations for T1621 are in place. If defenses are absent or misconfigured, this technique may be exploitable.

3. Execute Test: Use tools and methods described in the MITRE ATT&CK page and external references below.