Threat Response Unit

Tycoon 2FA Infrastructure Update: Threat Actors Adapt Following Global Coalition Takedown

eSentire Threat Response Unit (TRU)

April 1, 2026

9 MINS READ

What did we find?

Following the organized global coalition takedown of Tycoon 2FA phishing infrastructure led by Microsoft in coordination with industry partners including eSentire, our Threat Response Unit (TRU) has observed significant changes in the threat actors' tactics and infrastructure. Although many tactics mirror those outlined in our earlier analysis, "Phish & Chips: Serving Up Tycoon 2FA's Secrets", this blog introduces new technical indicators to help organizations detect and defend against this evolving Phishing-as-a-Service (PhaaS) threat.

Key Takeaways:

Figure 1 – ProxyLine website advertising global proxy coverage
Figure 1 – ProxyLine website advertising global proxy coverage

Authentication Source Infrastructure Evolution

Observations in this section are derived from Microsoft Entra ID sign‑in telemetry, enabling analysis of source infrastructure, user agents, and ASN‑level patterns.

Pre-Takedown Infrastructure

Prior to the coordinated takedown of Tycoon 2FA infrastructure, initial login attempts associated with Tycoon 2FA campaigns were commonly observed as originating from the following ASNs:

Sign-in attempts were associated with the following technical indicators:

Post-Takedown Infrastructure

Following the takedown, threat actors quickly pivoted to new infrastructure providers, with login attempts originating from the following ASNs:

Technical Indicators:

Notably, the user agent used in login attempts has been updated to the latest Axios version (1.13.6), suggesting the phishing kit is actively maintained and evolving. Additionally, analysis of post‑takedown Tycoon 2FA authentication activity shows heavy reliance on ProxyLine infrastructure for the majority of newly observed source IPs.

However, continued authentication attempts originating from AS9009 (M247 Europe SRL) were observed independently of ProxyLine, indicating that Tycoon 2FA operators are leveraging multiple authentication infrastructure sources in parallel.

ProxyLine Infrastructure Analysis

ProxyLine (proxyline[.]net) is a commercial datacenter proxy service that provides the underlying infrastructure for the majority of newly observed post‑takedown Tycoon 2FA authentication activity, as identified through Entra ID sign‑in telemetry. The service offers IPv4/IPv6 proxies with HTTP and SOCKS5 support and is distributed across an extensive global network.

Figure 2 – ProxyLine global country coverage
Figure 2 – ProxyLine global country coverage

ProxyLine advertises proxy coverage across 100+ countries spanning six continents, including Russia, Ukraine, USA, major European nations (Germany, UK, France, Italy, Spain), Asia-Pacific (Australia, China, India, Japan), and numerous other regions. This extensive geographic footprint allows threat actors to rotate through exit nodes worldwide, significantly complicating attribution and geographic-based blocking efforts.

In Gmail-targeted phishing campaigns, we have observed ProxyLine infrastructure usage (specifically via AS214238 (HOST TELECOM LTD)) since at least February 2026, predating takedown efforts.

ProxyLine's low-cost commercial service model makes it widely accessible to a variety of threat actors. The pricing table for this service is shown in the figure below.

Figure 3 – ProxyLine service pricing
Figure 3 – ProxyLine service pricing

ProxyLine offers several features that make it attractive to threat actors, including:

Evasion Techniques

Using Microsoft 365 Phishing Pages to Block Security Vendors

Our analysis reveals that Tycoon 2FA operators have implemented evasion mechanisms to avoid detection by security researchers and automated analysis systems. The phishing page queries ipinfo.io to identify the visitor's external IP and associated ASN/organization. Requests originating from Leaseweb, M247, Cloudflare (AS13335), Google, or Microsoft are redirected to the legitimate Carrefour website, helping conceal the phishing content from security researchers and automated analysis systems that operate from those infrastructure providers.

Figure 4 – Victim geolocation tracking implementation in Microsoft 365 phishing page
Figure 4 – Victim geolocation tracking implementation in Microsoft 365 phishing page

In some cases, we have also observed Tycoon 2FA leverage geojs.io for capturing victim IP address and country information to enrich stolen credentials with geographic context.

Figure 5 – Victim geolocation tracking implementation in Microsoft 365 phishing page (old but active)
Figure 5 – Victim geolocation tracking implementation in Microsoft 365 phishing page (old but active)

The following CyberChef recipe can be used to decrypt credentials in transit, as Tycoon 2FA continues to use the same AES key and IV referenced in our previous blog, "Phish & Chips: Serving Up Tycoon 2FA's Secrets".

From_Base64('A-Za-z0-9+/=',true,false)
AES_Decrypt({'option':'Latin1','string':'1234567890123456'},{'option':'Latin1','string':'1234567890123456'},'CBC','Raw','Raw',{'option':'Hex','string':''},{'option':'Hex','string':''})

Gmail Phishing Pages - Alternative Evasion Method

Similar blocking logic is employed for Gmail-targeted phishing pages, using api.ipapi.is as the IP intelligence source. In observed incidents, victims were redirected to legitimate websites like Kajabi[.]com, as shown in the figure below.

Figure 6 – Victim geolocation tracking in Gmail phishing page + cloud evasion with redirect to legitimate site
Figure 6 – Victim geolocation tracking in Gmail phishing page + cloud evasion with redirect to legitimate site

WebSocket Communication in Google Phishing

We've observed the implementation of WebSocket-based communication in Gmail-targeted phishing campaigns.

Figure 7 – WebSocket communication during Gmail phishing session
Figure 7 – WebSocket communication during Gmail phishing session

WebSocket usage enables:

Phishing Kit Code Analysis

Despite the infrastructure diversification and operational adaptations described above, source code analysis reveals minimal functional changes to the Tycoon 2FA phishing kit between pre-takedown and post-takedown versions.

Figure 8 – Tycoon 2FA source code comparison - core components remain unchanged post-takedown
Figure 8 – Tycoon 2FA source code comparison - core components remain unchanged post-takedown

The comparison above demonstrates that three critical components remain functionally identical:

This complete code consistency indicates threat actors prioritized operational continuity over kit redevelopment, maintaining the same codebase while exclusively pivoting infrastructure.

ASN Distribution Analysis – Authentication Source Infrastructure

Our incident data shows a clear shift in ASN usage following takedown efforts, with Tycoon 2FA operators improving operational resilience by making use of several new infrastructure providers.

The figure below (a stacked bar graph of ASNs by date) highlights this rapid infrastructure adaptation, and the need for continued vigilance to detect and disrupt campaigns.

Figure 9 – Distribution of phishing sessions across ASNs showing infrastructure pivot after Microsoft takedown
Figure 9 – Distribution of phishing sessions across ASNs showing infrastructure pivot after Microsoft takedown

What did we do?

What can you learn from this TRU Positive?

Recommendations from our Threat Response Unit (TRU):

Indicators of Compromise

Detailed Indicators of Compromise (IOCs) including IP addresses, domains, and URLs, are available in our threat intelligence repository here.

Advanced KQL Hunting Query:

let aadFunc = (tableName: string) {
    table(tableName)
    | where ResultType == 0 and AppDisplayName == ('OfficeHome')
    | where UserAgent contains 'axios'
    | limit 100
    | extend risks = todynamic(RiskEventTypes_V2)
    | extend risk = iif(isnull(risks) or array_length(risks) == 0, dynamic([null]), risks)
    | mv-expand risk
    | summarize first_time = min(TimeGenerated), last_time = max(TimeGenerated),
        IPAddresses = make_list(IPAddress), risks = make_set(risk)
        by UserPrincipalName,AppDisplayName,UserAgent
};
let aadSignin = aadFunc("SigninLogs");
let aadNonInt = aadFunc("AADNonInteractiveUserSignInLogs");
union aadSignin, aadNonInt

Key IOCs:

ASNs of Interest:

External Legitimate Services Used by Tycoon 2FA:

Check Domain:
 

page.url:/.*\..*\.[a-z]{2,10}\/[a-zA-Z0-9]{1,20}[~!@$][a-zA-Z0-9]{1,20}/

References

To learn how your organization can build cyber resilience and prevent business disruption with eSentire’s Next Level MDR, connect with an eSentire Security Specialist now.

GET STARTED

ABOUT ESENTIRE’S THREAT RESPONSE UNIT (TRU)

The eSentire Threat Response Unit (TRU) is an industry-leading threat research team committed to helping your organization become more resilient. TRU is an elite team of threat hunters and researchers that supports our 24/7 Security Operations Centers (SOCs), builds threat detection models across the eSentire XDR Cloud Platform, and works as an extension of your security team to continuously improve our Managed Detection and Response service. By providing complete visibility across your attack surface and performing global threat sweeps and proactive hypothesis-driven threat hunts augmented by original threat research, we are laser-focused on defending your organization against known and unknown threats.

Back to blog

Take Your Cybersecurity Program to the Next Level with eSentire MDR.

BUILD A QUOTE

Read Similar Blogs

EXPLORE MORE BLOGS