APT28 Router DNS Hijacking Campaign Disrupted by FBI
The FBI disrupted an APT28 operation that compromised internet-connected routers to enable DNS hijacking, according to reporting citing U.S. and UK government findings. The campaign abused vulnerable edge devices to alter DNS settings and redirect traffic, giving the Russian state-linked group a way to intercept victim communications, harvest credentials, and support follow-on espionage activity. The activity was significant enough to prompt public warnings from the FBI and the UK NCSC, which described router exploitation as a key enabler for the hijacking operations.
Government guidance tied the operation to exploitation of routers exposed to the internet and urged organizations to harden perimeter infrastructure by patching devices, restricting remote administration, rotating credentials, and reviewing DNS configurations for unauthorized changes. The disclosures underscore how Russian espionage actors continue to rely on stealthy network-level tradecraft—using compromised infrastructure rather than malware alone—to persist in victim environments and covertly redirect or monitor traffic.

Get ahead of threats like this
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
How this story unfolded
3 events from the most recent confirmed update back to the earliest known activity.
FBI disrupts APT28 router-based DNS hijacking network
By 2026-04-08, reporting indicated that the FBI had disrupted an APT28 operation that exploited routers to enable DNS hijacking. An accompanying NCSC reference indicates official attention to APT28's router exploitation tradecraft in support of these operations.
FireEye publicly documents APT29's TOR domain-fronting tradecraft
On 2017-03-27, FireEye published technical details on APT29's use of TOR, meek domain fronting, fake Google-themed directories, port forwarding of RDP/SMB-related services, Sticky Keys abuse, and a 'Google Update' persistence service. The report highlighted how the technique hindered network detection and emphasized the need for endpoint visibility.
APT29 uses TOR domain fronting to maintain covert access
FireEye reported that APT29 had used TOR with the meek domain-fronting plugin for at least two years to preserve stealthy backdoor access in victim environments. The traffic was made to resemble legitimate HTTPS connections to Google services while tunneling attacker communications through TOR.
Sources
4 references tracked. Mallory keeps watching after this page renders.
APT28 DNS Hijacking: FBI Disrupts Router Attack Network
thecyberexpress.com
Open sourceAPT29 Domain Fronting With TOR " APT29 Domain Fronting With TOR | FireEye Inc
web.archive.org
Open sourceAPT29 Domain Fronting With TOR | FireEye Inc
fireeye.com
Open sourceNcsc Blog
ncsc.gov.uk
Open sourceSee the full picture, correlated to your attack surface.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.


