{"id":45197,"date":"2026-04-08T00:06:32","date_gmt":"2026-04-07T16:06:32","guid":{"rendered":"https:\/\/nuoya.nuoyayasuo.top\/index.php\/2026\/04\/08\/authorities-disrupt-router-dns-hijacks-used-to-steal-microsoft-365-logins\/"},"modified":"2026-04-08T00:06:32","modified_gmt":"2026-04-07T16:06:32","slug":"authorities-disrupt-router-dns-hijacks-used-to-steal-microsoft-365-logins","status":"publish","type":"post","link":"https:\/\/nuoya.nuoyayasuo.top\/index.php\/2026\/04\/08\/authorities-disrupt-router-dns-hijacks-used-to-steal-microsoft-365-logins\/","title":{"rendered":"Authorities disrupt router DNS hijacks used to steal Microsoft 365 logins"},"content":{"rendered":"\n

\"Authorities<\/p>\n

An international operation from law enforcement authorities in partnership with private companies has disrupted FrostArmada, an APT28 campaign hijacking local traffic from MikroTik and TP-Link routers to steal Microsoft account credentials.<\/p>\n

The Russian threat group APT28, also tracked as Fancy Bear, Sofacy, Forest Blizzard, Strontium, Storm-2754, and Sednit, has been linked to Russia’s General Staff Main Intelligence Directorate (GRU) 85th Main Special Service Center (GTsSS) military unit 26165.<\/p>\n

In the FrostArmada attacks, the hackers compromised mainly small office\/home office (SOHO) routers and altered the domain name system (DNS) settings to point to virtual private servers (VPS) under their control, which acted as DNS resolvers.<\/p>\n

\"Authorities<\/a> <\/div>\n

This allowed APT28 to intercept authentication traffic to targeted domains and steal Microsoft logins and OAuth tokens.<\/p>\n

At its peak in December 2025, FrostArmada infected 18,000 devices across 120 countries, primarily targeting government agencies, law enforcement, IT and hosting providers, and organizations operating their own servers.<\/p>\n

Microsoft, whose services were targeted by this campaign, worked together with Black Lotus Labs (BLL), Lumen’s threat research and operations division, to map the malicious activity and identify victims.<\/p>\n

With support from the FBI, the U.S. Department of Justice, and the Polish government, the offending infrastructure has been taken offline.<\/p>\n

FrostArmada activity<\/h3>\n

The attackers targeted internet-exposed routers, primarily MikroTik and TP-Link, as well as some firewall products from Nethesis and older Fortinet models.<\/p>\n

Once compromised, the devices communicated with the attackers’ infrastructure and received DNS configuration changes that redirected traffic to malicious VPS nodes.<\/p>\n

The new DNS settings were automatically pushed to internal devices via the Dynamic Host Configuration Protocol (DHCP).<\/p>\n

When clients queried authentication-related domains the threat actor targeted, the DNS server returned the attacker’s IP instead of the real one, redirecting victims to an adversary-in-the-middle (AitM) proxy.<\/p>\n

\n
\"Authorities
DNS request redirection at the router level<\/strong>
Source: Black Lotus Labs<\/em><\/figcaption><\/figure>\n<\/div>\n

The only visible sign of fraud for the victim would have been a warning for an invalid TLS certificate, which could have easily been dismissed. However, ignoring the alert gave the threat actor access to the victim’s unencrypted internet communication.<\/p>\n

“The actor essentially ran a proxy service as the AitM that the end user was directed to via DNS,” Lumen’s Black Lotus Labs researchers explain.<\/p>\n

“The only sign of this attack would be a pop-up warning about connecting to an untrusted source because of the ‘break and inspect’ configuration.”<\/p>\n

“If warnings were present and ignored or clicked through, the actor proxied requests to the legitimate services, collecting the data at the midpoint and collecting data associated with the targeted account by passing the valid OAuth token.”<\/p>\n

In some cases, though, the hackers spoofed DNS responses for certain domains, thus forcing affected endpoints to connect to the attack infrastructures, Microsoft says in a report<\/a> today.<\/p>\n

Lumen reports that FrostArmada operated in two distinct clusters, one called the ‘Expansion team’ dedicated to device compromise and botnet growth, and the second handling the AiTM and credential collection operations.<\/p>\n

\n
\"Authorities
Overview of the Expansion branch operations<\/strong>
Source: Black Lotus Labs<\/em><\/figcaption><\/figure>\n<\/div>\n

The researchers report that FrostArmada activity increased sharply following an August 2025 report from the National Cyber Security Centre (NCSC) in the UK describing a Forest Blizzard toolset that targeted Microsoft account credentials and tokens.<\/p>\n

Microsoft confirmed that APT28 carried out AitM attacks against domains associated with the Microsoft 365 service, as subdomains for Microsoft Outlook on the web have also been targeted.<\/p>\n

Additionally, the company observed this activity on servers belonging to three government organizations in Africa that were not hosted on Microsoft infrastructure. In those attacks, “Forest Blizzard intercepted DNS requests and conducted follow-on collection.”<\/p>\n

Black Lotus Labs also observed the threat actor targeting entities with on-premise email servers and “a small number of government organizations” in North Africa, Central America, and Southeast Asia.<\/p>\n

The researchers note that “there was also a connection to a national identity platform in one European country.”<\/p>\n

In a report today, the UK agency says<\/a> that the AitM activity impacted both browser sessions and desktop applications, and the DNS hijacking is believed to have been opportunistic in nature to build a large pool of potential targets and then filtering those of interest.<\/p>\n

Black Lotus Labs has published a small set of indicators of compromise<\/a> for the VPS servers used during the FrostArmada campaign:<\/p>\n\n\n\n\n\n\n\n\n\n\n
IP address<\/th>\nFirst Seen<\/th>\nLast Seen<\/th>\n<\/tr>\n<\/thead>\n
64.120.31[.]96<\/td>\nMay 19, 2025<\/td>\nMarch 31, 2026<\/td>\n<\/tr>\n
79.141.160[.]78<\/td>\nJuly 19, 2025<\/td>\nMarch 31, 2026<\/td>\n<\/tr>\n
23.106.120[.]119<\/td>\nJuly 19, 2025<\/td>\nMarch 31, 2026<\/td>\n<\/tr>\n
79.141.173[.]211<\/td>\nJuly 19, 2025<\/td>\nMarch 31, 2026<\/td>\n<\/tr>\n
185.117.89[.]32<\/td>\nSeptember 9, 2025<\/td>\nSeptember 9, 2025<\/td>\n<\/tr>\n
185.237.166[.]55<\/td>\nDecember 30, 2025<\/td>\nDecember 30, 2025<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The researchers note that defenders should implement certificate pinning for corporate devices (laptops, mobile phones) controlled via an MDM solution, which would generate an error when the attacker tries to intercept and analyze traffic on their VPS infrastructure.<\/p>\n

Another recommendation is to minimize the attack surface through patching, limiting exposure on the public web, and removing all end-of-life equipment.<\/p>\n

Microsoft<\/a> and the NCSC<\/a> also provide a list of IoCs and protection guidance to help defenders identify and prevent DNS hijacking attacks.<\/p>\n