A threat actor linked to the Chinese state-sponsored group Mustang Panda is running an espionage campaign against targets in Thailand, using a familiar lure — a document promising an Indo-Pacific regional assessment — to deliver a substantially rebuilt version of a backdoor known as LOTUSLITE. The new variant, dubbed LOTUSLITE V2, swaps the malware family’s original C++ codebase for managed C#, and hides its execution behind a legitimate, trusted PDF application.
The campaign was documented in a November 15, 2026 technical analysis from Antares Research, whose authors — Kyaw Pyiyt Htet and Phyo Paing Htun — assessed with high confidence that the malware is a modernized successor to the original LOTUSLITE family, based on shared protocol design choices, overlapping execution and persistence techniques, and consistent regional targeting patterns. That lineage, rather than geography alone, is what ties the activity back to Mustang Panda, a group also tracked under the name Earth Preta.
A Cloud File Link as the Opening Move
The infection begins with a publicly accessible Zoho WorkDrive link that, once clicked, immediately downloads a ZIP archive themed around the promised assessment document. Using a legitimate, widely trusted business file-sharing platform as the delivery mechanism gives the download an air of normalcy that a direct email attachment or unfamiliar website might not provide. It’s worth noting that this incident involves abuse of a standard public sharing link on Zoho’s platform, not any underlying vulnerability in Zoho WorkDrive itself — a distinction that matters, since other unrelated campaigns have separately abused the same platform to spread entirely different malware families like PureRAT.
Inside the archive sit two files: an executable disguised to look like the promised assessment tool, and a companion malicious library sitting alongside it. Downloading the archive alone does nothing — the infection only proceeds once a victim actually runs the disguised executable. How the WorkDrive link was initially delivered to targets — whether through email, messaging, or another channel — isn’t established in the available research.
Borrowing a Trusted Application’s Signature
Once launched, the disguised executable stages its components inside a directory made to look like it belongs to Microsoft, tucked beneath the ProgramData folder. From there, it relies on a technique called DLL sideloading: a genuine, digitally signed PDFgear application is used to load the malicious library sitting in that same staged directory. The PDFgear binary’s valid signature doesn’t extend any trust to the library beside it — a nuance that matters for anyone reviewing process trees and assuming a signed executable means safe activity nearby.
For persistence, the malware checks its own privilege level: if running with SYSTEM rights, it creates a machine-wide registry Run key; otherwise, it falls back to the current user’s own startup entry. As a secondary foothold, it also hijacks PDFgear’s default file association for PDF documents, redirecting it to an attacker-controlled launcher that still forwards along the originally selected file so the redirection isn’t immediately obvious to the user.
A More Resilient Communication Layer
The shift from LOTUSLITE’s original native C++ build to managed C# brings more than just a different programming language — it comes with reworked network communications. Two command-and-control addresses are hardcoded into the implant, stored as byte arrays and decoded at runtime using a simple single-byte XOR operation. The malware supports both UDP and secure WebSocket connections across a range of ports, with connection retry intervals that progressively lengthen over time, likely as a way to avoid generating easily-flagged, rapid-fire network noise.
On top of whatever transport-level encryption a WebSocket connection already provides, LOTUSLITE V2 adds its own application-layer encryption using AES-256-GCM, meaning the payload itself stays encrypted even if the outer connection is somehow intercepted or decrypted. The malware implements this cryptography by calling Windows’ native cryptographic functions directly through a compatibility wrapper, a design researchers say is meant to keep the backdoor working reliably even on older, unpatched Windows endpoints that might not fully support .NET’s higher-level encryption libraries.
Detection Guidance
Antares Research notes that detection signatures built around LOTUSLITE’s earlier protocol markers will not catch this updated version, since the implant now uses a different versioned packet identifier. Security teams are advised to correlate several specific behaviors rather than rely on any single indicator: unexpected PDFgear execution events, unusual registry modifications tied to startup persistence, unexplained library loading alongside otherwise legitimate signed applications, and outbound network connections that can be directly attributed to the staged executable’s own process rather than judged solely by destination IP address. This campaign is a reminder that threat actors frequently keep their delivery infrastructure — in this case, cloud storage abuse — separate from their backdoor’s actual command infrastructure, and defenders who conflate the two risk missing the real indicators of compromise.
Leave a Reply
You must be logged in to post a comment.