Security

DNS Hijacking Attacks via SOHO Routers: Microsoft Warns

3 min read

Summary

Microsoft Threat Intelligence says Forest Blizzard has been compromising vulnerable home and small-office routers to hijack DNS traffic and, in some cases, enable adversary-in-the-middle attacks against targeted connections. The campaign matters to IT teams because unmanaged SOHO devices used by remote and hybrid workers can expose cloud access and sensitive data even when corporate environments remain secure.

Need help with Security?Talk to an Expert

Introduction

Microsoft has disclosed a large-scale campaign in which Forest Blizzard, a threat actor linked to Russian military intelligence, compromised vulnerable SOHO routers and changed their DNS settings. For organizations with remote and hybrid workers, this is a critical reminder that unmanaged home and small-office network gear can become a blind spot that exposes Microsoft 365 access and other sensitive traffic.

What’s new

According to Microsoft Threat Intelligence, the actor has been active since at least August 2025 and has used compromised edge devices to build malicious DNS infrastructure at scale.

Key findings

  • Forest Blizzard altered router configurations to point devices to actor-controlled DNS resolvers.
  • Microsoft identified more than 200 organizations and 5,000 consumer devices affected by the malicious DNS infrastructure.
  • The campaign enabled passive DNS collection and reconnaissance across targeted networks.
  • In a subset of cases, the actor used this position to support Transport Layer Security (TLS) adversary-in-the-middle (AiTM) attacks.
  • Microsoft observed follow-on targeting of Outlook on the web domains and separate AiTM activity against government servers in Africa.

Why this matters for IT administrators

The most important takeaway is that enterprise security controls do not fully protect traffic if a user’s upstream router is compromised. A home or small-office router can silently redirect DNS lookups, giving an attacker visibility into requested domains and, in selected scenarios, the opportunity to spoof responses and attempt traffic interception.

For Microsoft 365 customers, this is especially relevant where users access Outlook on the web or other cloud services from unmanaged networks. Even if Microsoft services themselves are not compromised, users may still be exposed if they ignore invalid TLS certificate warnings or if suspicious DNS activity goes undetected.

Microsoft recommends several immediate mitigation steps:

  • Review risks tied to remote users’ home and small-office networking equipment.
  • Enforce trusted DNS resolution where possible, including Zero Trust DNS (ZTDNS) controls on Windows endpoints.
  • Enable network protection and web protection in Microsoft Defender for Endpoint.
  • Block known malicious domains and retain detailed DNS logs for monitoring and investigation.
  • Audit router and edge device configurations, especially DNS and DHCP settings.
  • Ensure vulnerable SOHO devices are patched, securely configured, or replaced if no longer supported.
  • Train users not to bypass TLS certificate warnings.

Bottom line

This campaign shows how attackers can exploit weakly managed edge devices to gain visibility into higher-value enterprise targets. Security teams should expand their threat model beyond corporate infrastructure and account for home-office networking equipment as part of remote access and Microsoft 365 protection strategies.

Need help with Security?

Our experts can help you implement and optimize your Microsoft solutions.

Talk to an Expert

Stay updated on Microsoft technologies

DNS hijackingSOHO routersMicrosoft DefenderAiTMForest Blizzard

Related Posts

Security

Microsoft Sentinel Named a 2026 SIEM Leader

Microsoft has been named a Leader in the 2026 Gartner Magic Quadrant for SIEM, highlighting the continued momentum behind Microsoft Sentinel. The announcement also underscores Microsoft's push toward integrated, AI-powered security operations through deep Sentinel integration with the new Integrated Security Operations Center in Microsoft Defender.

Security

Microsoft Perception GA: Agentic Security at Ignite

Microsoft has made Microsoft Perception generally available, introducing an agentic security platform that coordinates red, blue, and green team agents through automated playbooks. Announced at Ignite 2026, the update also expands Defender and Sentinel capabilities to help security teams detect, investigate, and remediate AI-speed threats while keeping administrators in control.

Security

Device Code Phishing Risks for AI Coding Agents

Microsoft warns that device code phishing can be used against AI coding agents such as GitHub Copilot CLI, not just user mailboxes or cloud apps. In a controlled lab, a single approved device code sign-in could enable remote session steering, memory poisoning, synced session exposure, and private repository access depending on account permissions and enabled features.

Security

Microsoft 365 Outage Phishing Campaign Targets Users

Microsoft Threat Intelligence reported a high-volume phishing campaign that impersonates Microsoft 365 service-health notifications to trick users into clicking malicious links. The campaign matters because it uses outage-themed urgency and recipient-specific tracking to target multiple industries, increasing the risk of credential theft and follow-on account compromise.

Security

SCKit ScreenConnect Attack: MSPs Must Hunt Now

Microsoft Threat Intelligence confirmed a campaign abusing ConnectWise ScreenConnect to deploy unauthorized remote-access clients and the SCKit worm on MSP-managed endpoints. The activity can also target technician sessions, making this a high-priority incident for defenders because removing a rogue client alone does not eliminate persistence or invalidate exposed sessions.

Security

AI Agent Supply Chain Attacks Target Coding Tools

Microsoft Security researchers detailed two post-training supply chain attack paths that can backdoor coding and terminal agents: dataset poisoning and model poisoning. The findings matter because compromised agents can misuse tools, execute commands, and access sensitive environments even when prompts appear benign, reinforcing the need for stronger controls around training data, model provenance, and tool permissions.