CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

Tycoon2FA post-takedown resurgence

campaign · campaign:tycoon2fa-oauth-device-authorization-grant-microsoft-365-post-takedown single-source

Tycoon2FA phishing-as-a-service resurgence after its March 2026 takedown, abusing the OAuth Device Authorization Grant against Microsoft 365.

Coverage
1
first 2026-05-18 → last 2026-10-21
Latest activity
2026-05-18
Tycoon 2FA adds device-code phishing: victims approve token issuance to an attacker device on genuine…
Peak priority
high
1 high
Targets
·
no sector or region stated
Sources cited
3
3 hosts

Defender insights

What each entry about Tycoon2FA post-takedown resurgence tells a defender to do, newest first.

2026-05-18HIGHTycoon 2FA adds device-code phishing: victims approve token issuance to an attacker device on genuine Microsoft pages

Exposure · triage · detection

Story timeline

  1. 2026-05-18Tycoon 2FA after the March 2026 takedown: operators add OAuth device-code phishing against Microsoft 365 alongside the credential-relay kit
    deep-diveTycoon 2FA adds device-code phishing: victims approve token issuance to an attacker device on genuine Microsoft pages
ATT&CK techniques (9 across 9 tactics)

9 techniques observed across 1 entry about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.1 · compare on the matrix · Navigator layer (JSON)

  • Resource DevelopmentAcquire Infrastructure: Serverless
  • Initial AccessValid Accounts: Cloud Accounts · Phishing: Spearphishing Link
  • ExecutionUser Execution: Malicious Link
  • PersistenceValid Accounts: Cloud Accounts
  • Privilege EscalationValid Accounts: Cloud Accounts
  • StealthObfuscated Files or Information · Valid Accounts: Cloud Accounts · Virtualization/Sandbox Evasion · Debugger Evasion
  • Credential AccessSteal Application Access Token
  • DiscoveryVirtualization/Sandbox Evasion · Debugger Evasion
  • Lateral MovementUse Alternate Authentication Material: Application Access Token

Resource Development TA0042

T1583.007Acquire Infrastructure: Serverless×1

Adversaries may purchase and configure serverless cloud infrastructure, such as Cloudflare Workers, AWS Lambda functions, or Google Apps Scripts, that can be used during targeting. By utilizing serverless infrastructure, adversaries can make it more difficult to attribute infrastructure used during operations back to them.

Evidence: 2026-05-18/tycoon2fa-after-the-march-2026-takedown-oauth-device-authori · ATT&CK page ↗

Initial Access TA0001

T1078.004Valid Accounts: Cloud Accounts×1

Valid accounts in cloud environments may allow adversaries to perform actions to achieve Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Cloud accounts are those created and configured by an organization for use by users, remote support, services, or for administration of resources within a cloud service provider or SaaS application. Cloud Accounts can exist solely in the cloud; alternatively, they may be hybrid-joined between on-premises systems and the cloud through syncing or federation with other identity sources such as Windows Active Directory.

Evidence: 2026-05-18/tycoon2fa-after-the-march-2026-takedown-oauth-device-authori · ATT&CK page ↗

T1566.002Phishing: Spearphishing Link×1

Adversaries may send spearphishing emails with a malicious link in an attempt to gain access to victim systems. Spearphishing with a link is a specific variant of spearphishing. It is different from other forms of spearphishing in that it employs the use of links to download malware contained in email, instead of attaching malicious files to the email itself, to avoid defenses that may inspect email attachments. Spearphishing may also involve social engineering techniques, such as posing as a trusted source.

Evidence: 2026-05-18/tycoon2fa-after-the-march-2026-takedown-oauth-device-authori · ATT&CK page ↗

Execution TA0002

T1204.001User Execution: Malicious Link×1

An adversary may rely upon a user clicking a malicious link in order to gain execution. Users may be subjected to social engineering to get them to click on a link that will lead to code execution. This user action will typically be observed as follow-on behavior from Spearphishing Link. Clicking on a link may also lead to other execution techniques such as exploitation of a browser or application vulnerability via Exploitation for Client Execution. Links may also lead users to download files that require execution via Malicious File.

Evidence: 2026-05-18/tycoon2fa-after-the-march-2026-takedown-oauth-device-authori · ATT&CK page ↗

Persistence TA0003

T1078.004Valid Accounts: Cloud Accounts×1

Valid accounts in cloud environments may allow adversaries to perform actions to achieve Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Cloud accounts are those created and configured by an organization for use by users, remote support, services, or for administration of resources within a cloud service provider or SaaS application. Cloud Accounts can exist solely in the cloud; alternatively, they may be hybrid-joined between on-premises systems and the cloud through syncing or federation with other identity sources such as Windows Active Directory.

Evidence: 2026-05-18/tycoon2fa-after-the-march-2026-takedown-oauth-device-authori · ATT&CK page ↗

Privilege Escalation TA0004

T1078.004Valid Accounts: Cloud Accounts×1

Valid accounts in cloud environments may allow adversaries to perform actions to achieve Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Cloud accounts are those created and configured by an organization for use by users, remote support, services, or for administration of resources within a cloud service provider or SaaS application. Cloud Accounts can exist solely in the cloud; alternatively, they may be hybrid-joined between on-premises systems and the cloud through syncing or federation with other identity sources such as Windows Active Directory.

Evidence: 2026-05-18/tycoon2fa-after-the-march-2026-takedown-oauth-device-authori · ATT&CK page ↗

Stealth TA0005

T1027Obfuscated Files or Information×1

Adversaries may attempt to make an executable or file difficult to discover or analyze by encrypting, encoding, or otherwise obfuscating its contents on the system or in transit. This is common behavior that can be used across different platforms and the network to evade defenses.

Evidence: 2026-05-18/tycoon2fa-after-the-march-2026-takedown-oauth-device-authori · ATT&CK page ↗

T1078.004Valid Accounts: Cloud Accounts×1

Valid accounts in cloud environments may allow adversaries to perform actions to achieve Initial Access, Persistence, Privilege Escalation, or Defense Evasion. Cloud accounts are those created and configured by an organization for use by users, remote support, services, or for administration of resources within a cloud service provider or SaaS application. Cloud Accounts can exist solely in the cloud; alternatively, they may be hybrid-joined between on-premises systems and the cloud through syncing or federation with other identity sources such as Windows Active Directory.

Evidence: 2026-05-18/tycoon2fa-after-the-march-2026-takedown-oauth-device-authori · ATT&CK page ↗

T1497Virtualization/Sandbox Evasion×1

Adversaries may employ various means to detect and avoid virtualization and analysis environments. This may include changing behaviors based on the results of checks for the presence of artifacts indicative of a virtual machine environment (VME) or sandbox. If the adversary detects a VME, they may alter their malware to disengage from the victim or conceal the core functions of the implant. They may also search for VME artifacts before dropping secondary or additional payloads. Adversaries may use the information learned from Virtualization/Sandbox Evasion during automated discovery to shape follow-on behaviors.

Evidence: 2026-05-18/tycoon2fa-after-the-march-2026-takedown-oauth-device-authori · ATT&CK page ↗

T1622Debugger Evasion×1

Adversaries may employ various means to detect and avoid debuggers. Debuggers are typically used by defenders to trace and/or analyze the execution of potential malware payloads.

Evidence: 2026-05-18/tycoon2fa-after-the-march-2026-takedown-oauth-device-authori · ATT&CK page ↗

Credential Access TA0006

T1528Steal Application Access Token×1

Adversaries can steal application access tokens as a means of acquiring credentials to access remote systems and resources.

Evidence: 2026-05-18/tycoon2fa-after-the-march-2026-takedown-oauth-device-authori · ATT&CK page ↗

Discovery TA0007

T1497Virtualization/Sandbox Evasion×1

Adversaries may employ various means to detect and avoid virtualization and analysis environments. This may include changing behaviors based on the results of checks for the presence of artifacts indicative of a virtual machine environment (VME) or sandbox. If the adversary detects a VME, they may alter their malware to disengage from the victim or conceal the core functions of the implant. They may also search for VME artifacts before dropping secondary or additional payloads. Adversaries may use the information learned from Virtualization/Sandbox Evasion during automated discovery to shape follow-on behaviors.

Evidence: 2026-05-18/tycoon2fa-after-the-march-2026-takedown-oauth-device-authori · ATT&CK page ↗

T1622Debugger Evasion×1

Adversaries may employ various means to detect and avoid debuggers. Debuggers are typically used by defenders to trace and/or analyze the execution of potential malware payloads.

Evidence: 2026-05-18/tycoon2fa-after-the-march-2026-takedown-oauth-device-authori · ATT&CK page ↗

Lateral Movement TA0008

T1550.001Use Alternate Authentication Material: Application Access Token×1

Adversaries may use stolen application access tokens to bypass the typical authentication process and access restricted accounts, information, or services on remote systems. These tokens are typically stolen from users or services and used in lieu of login credentials.

Evidence: 2026-05-18/tycoon2fa-after-the-march-2026-takedown-oauth-device-authori · ATT&CK page ↗

Entries about Tycoon2FA post-takedown resurgence (1)

2026-05-18 · view entry permalink →

HIGHupdatedNATOB2

Tycoon 2FA after the March 2026 takedown: operators add OAuth device-code phishing against Microsoft 365 alongside the credential-relay kit

eSentire's Threat Response Unit analyzed in late April 2026 a campaign by operators of the Tycoon 2FA phishing-as-a-service kit, which kept running after the March 2026 takedown led by Microsoft and Europol, that keeps the kit's in-browser tradecraft but ends in Microsoft's legitimate device-login flow instead of a credential-relay proxy (eSentire TRU, 2026-05-12). The device-code variant runs beside the relay kit: eSentire still names the OfficeHome AppId as the primary marker of the credential-relay variant and treats the two AppIds as one detection set (eSentire TRU, 2026-05-12), and BleepingComputer reports that the kit now supports device-code phishing (BleepingComputer, 2026-05-17).

The lure, a forwarded vendor-invoice reminder, carries a Trustifi click-tracking URL whose clean-reputation domain launders the link, and Trustifi redirects to a throwaway Cloudflare Workers subdomain that returns an AES-GCM-encrypted page decrypted in the browser (eSentire TRU, 2026-05-12). The decrypted controller blanks the page for headless browsers and Burp, suppresses developer-tool shortcuts, redirects to microsoft.com when a debugger timing trap fires, checks the visitor's network owner against 230 cloud, sandbox, security-vendor, VPN and AI-crawler names, and stops rendering after a hardcoded expiry date (eSentire TRU, 2026-05-12). A Microsoft-branded fake CAPTCHA then queries a Tycoon 2FA Check Domain, which serves suspected analysts a benign decoy website and real victims a Microsoft 365 voicemail lure (eSentire TRU, 2026-05-12).

The voicemail page displays a user code that the operator's backend obtained from Microsoft's device-code endpoint, copies it and opens microsoft.com/devicelogin; the victim signs in at login.microsoftonline.com, approves the MFA push and consents to Microsoft Authentication Broker, and Microsoft issues access and refresh tokens to the operator's polling client, after which the kit sends the victim to their real Outlook inbox (eSentire TRU, 2026-05-12). A victim already signed in sees no authentication step at all, only the consent prompt (eSentire TRU, 2026-05-12). Because the Broker is a Microsoft first-party application it does not trigger unverified-publisher OAuth detections, and its token can be exchanged for Exchange, Graph and OneDrive tokens without further interaction (eSentire TRU, 2026-05-12). The backend traffic still uses the CryptoJS AES-CBC layer with a hardcoded key and IV unchanged since eSentire's April 2025 analysis, which works as a kit fingerprint rather than protection, and the operators' token traffic came from Alibaba (US) hosting, which eSentire has seen across both kit variants since about 2026-04-10 in addition to the hosting providers documented before (eSentire TRU, 2026-05-12).

Triage: a device-code sign-in alone can be a legitimate command-line tool or input-constrained device; eSentire's discriminators are a source with no prior device-code activity and Node.js user agents against the Broker AppId in non-interactive sign-ins, which it calls highly anomalous in production environments (eSentire TRU, 2026-05-12).

Doing so authorizes the attacker to register a rogue device with the victim’s Microsoft 365 account, giving them unrestricted access to the victim's data and services, including email, calendar, and cloud file storage.

BleepingComputer 2026-05-17

The user's MFA worked exactly as designed. There is no proxy, no credential capture, no fake Microsoft page; everything from login.microsoftonline.com onward is authentic Microsoft infrastructure responding to authentic Microsoft authentication events.

Successful device-code authentication (AuthenticationProtocol = deviceCode, ResultType = 0) from sources with no prior device-code activity.

eSentire Threat Response Unit 2026-05-12

We recommend organizations get as close as possible to a unilateral block on device code flow.

Microsoft Learn
Correctionrun 2026-10-21T1148Z-auditaffected_productsbodyclassificationentitiesevent_dateevidenceheadlineregionssectorssourcessourcing_notesummarytagstechniquestitleverification

Tycoon 2FA operators did not move away from the credential-relay kit: eSentire still names the OfficeHome AppId as the primary marker of the relay variant and treats it and the Broker AppId as one detection set, and BleepingComputer reports that the kit now supports device-code phishing (eSentire TRU, 2026-05-12; BleepingComputer, 2026-05-17). The Alibaba (US) hosting seen since about 2026-04-10 is an addition to the hosting providers documented before, not a replacement (eSentire TRU, 2026-05-12). The lure page shows a user code obtained by the operator's backend and tells the victim to paste it at microsoft.com/devicelogin (BleepingComputer, 2026-05-17), after which the victim sees a consent prompt reading "Are you trying to sign in to Microsoft Authentication Broker?" (eSentire TRU, 2026-05-12). The detection signals eSentire publishes are successful deviceCode sign-ins from sources with no prior device-code activity, tokens issued to the Microsoft Authentication Broker AppId, node or undici user agents in non-interactive sign-ins, and ResultType 50173 after revocation (eSentire TRU, 2026-05-12). eSentire says the phish does not bypass MFA but changes what MFA authorizes, and recommends blocking the device-code flow with Conditional Access as the control that removes the attack class (eSentire TRU, 2026-05-12), in line with Microsoft's advice to get as close as possible to a unilateral block (Microsoft Learn); no source says that FIDO2 sign-in defeats device-code phishing.

threat18 May 05:00Zsingle-sourceOpen finding →

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Deep dive1

Source distribution

  • bleepingcomputer.com1 (33%)
  • esentire.com1 (33%)
  • learn.microsoft.com1 (33%)