TA416 Expands Espionage Operations Across Europe With Web Bug

TA416 has launched a renewed wave of espionage operations targeting government and diplomatic personnel across Europe. This persistent threat actor’s latest campaign employs a methodical approach, blending subtle email-based reconnaissance with subsequent malware delivery. The strategy allows TA416 to identify engaged targets patiently before deploying more potent malicious payloads, as detailed in a From mid-2025 into early 2026, the China-aligned group targeted diplomatic missions to the EU and NATO across several European countries.

In March 2026, it also widened activity to government and diplomatic entities in the Middle East after conflict in Iran, suggesting its targeting shifts with major geopolitical events.

The web bug emails came from freemail accounts and used themes like humanitarian concerns, interview requests, collaboration proposals, and a Greenland article to attract diplomatic readers.

Each message used unique tracking URLs or image filenames so the actor could tell which targets opened or clicked the lure.

Proofpoint researchers noted that the group used web bugs, malicious archive links, freemail accounts, and compromised diplomatic or government mailboxes to reach victims.

They identified repeated changes in the early infection chain, but a consistent end goal: loading a customized PlugX backdoor through DLL sideloading.

The impact is serious because the operation is built for intelligence gathering, not smash-and-grab crime.

Web bugs reveal whether a target opened an email, while later stages can give the attackers remote access, host details, and a way to download more payloads or open a reverse shell.

Later campaigns heavily targeted mailboxes tied to delegations to the EU and NATO, not just ordinary government addresses.

Infection chain

One striking part of this campaign is how TA416 kept changing the doorway while keeping the same room behind it.

Between September 2025 and March 2026, Proofpoint saw fake Cloudflare Turnstile pages, abuse of Microsoft Entra ID OAuth redirects, and archives carrying a renamed MSBuild executable with a malicious C# project file.

In the earlier wave, fake Turnstile pages impersonated Microsoft login pages and led users to ZIP files on Microsoft Azure Blob Storage.

Those ZIP files used ZIP smuggling and LNK files to carve out and run the next stage, ending with a signed executable, a malicious DLL, and an encrypted payload that loaded PlugX into memory.

Later, TA416 abused legitimate Microsoft authorization URLs by registering third-party Entra ID applications and forcing an authorization failure.

That trick redirected victims to attacker-controlled download pages, helping the emails look safer to users and also bypass some URL reputation checks because the first link pointed to a trusted Microsoft domain.

By February 2026, the actor changed again and used archives hosted on Google Drive or compromised SharePoint.

These archives contained a renamed MSBuild executable and a malicious CSPROJ file that decoded Base64-encoded URLs, downloaded another sideloading package to the temp folder, and launched PlugX through a legitimate executable.

Recent PlugX variants also showed stronger evasion and persistence. Proofpoint reported that in March 2026 samples, the sideloading set was copied to C:UsersPublicCanon and a Run registry key named Canon was created for startup, while the loader used API hashing, junk code, and control-flow flattening to make analysis harder.

Once active, PlugX used HTTP-based command and control with RC4-encrypted traffic, sent basic host details to the server, and supported commands for downloading new payloads, changing timing values, opening a reverse shell, or uninstalling itself.

Organizations exposed to this kind of targeting should treat diplomatic-themed emails, unexpected cloud-hosted archives, and Microsoft login links that trigger downloads as high-risk.

Strong filtering for LNK, ZIP, RAR, and project files, blocking unnecessary MSBuild execution, monitoring Run registry changes, and hunting for PlugX-style HTTP traffic are sensible steps to reduce exposure.

Disabling automatic external image loading where practical and sandboxing archives from cloud links can also cut the value of the group’s web bug reconnaissance and early-stage delivery tricks.

Disclaimer: HackersRadar reports on cybersecurity threats and incidents for informational and awareness purposes only. We do not engage in hacking activities, data exfiltration, or the hosting or distribution of stolen or leaked information. All content is based on publicly available sources.