A malware family that most of the security industry assumed was dead has quietly come back to life. Retadup, a USB-spreading worm that French law enforcement dismantled in 2019 after disinfecting more than 850,000 infected machines, is once again active — and this time it’s being used to hand out a modern, GPU-evasive loader called CoffeeLoader.
The discovery comes from researchers at Securelist, who published a technical breakdown on November 16, 2026 connecting a resurrected Retadup infrastructure to recent CoffeeLoader activity. Importantly, the comeback did not happen overnight: the researchers traced the revived command-and-control domains back to 2024, meaning the infrastructure had been quietly operating for roughly two years before this latest connection to CoffeeLoader was confirmed.
An Old Worm, A New Owner?
Retadup first surfaced in 2017, built using the AutoIt and AutoHotkey scripting languages. Its spreading mechanism is simple but effective: it copies itself onto any USB flash drive or external storage device plugged into an infected machine, disguising its files and relying on malicious Windows shortcuts. When an unsuspecting user later plugs that same drive into a different computer and clicks the disguised shortcut, the worm takes hold on the new system as well. Crucially, this requires a person to actually open the planted shortcut — simply inserting an infected drive isn’t enough on its own.
After the 2019 law enforcement takedown, Retadup’s command infrastructure went silent for years. But Securelist found that at least one surviving 2017-era infection was still successfully reaching out to newly re-registered versions of its old command domains in 2026 — strong evidence that someone, whether the original operator or a new party who simply bought up the expired domains, deliberately brought the network back online. The protocol Retadup uses to receive instructions is notably unsophisticated, relying on plain text that’s Base64-encoded and then converted to hexadecimal, which makes attribution to a specific operator difficult.
The revived infrastructure initially pushed out SmokeLoader before switching over to CoffeeLoader in early 2025. According to Kaspersky’s telemetry, roughly 15,000 Retadup infection attempts were blocked during the first three quarters of 2026 alone, concentrated heavily in Peru, Angola, Russia, and Bolivia. It’s worth noting these figures represent blocked infection attempts, not confirmed CoffeeLoader compromises.
CoffeeLoader’s New Tricks
The CoffeeLoader variant tied to this campaign shows real engineering effort. Its installer drops a tampered copy of a legitimate code library belonging to the popular 7-Zip archive utility and launches it through a trusted Windows system tool — not because of any actual flaw in 7-Zip, but because attackers swapped out part of that library’s code with self-decrypting shellcode from an updated packer known as Armoury.
Earlier versions of Armoury leaned on OpenCL to offload payload decryption to the graphics card — a technique designed specifically to dodge security sandboxes that lack real GPU hardware. The newer variant switches to OpenGL, a graphics API more commonly associated with rendering software, likely in another attempt to blend in and evade behavioral detection tools that watch for suspicious GPU usage patterns.
Once running, an intermediate downloader stage handles installation, sets up persistence, injects itself into legitimate Windows processes, and ultimately retrieves CoffeeLoader’s main component. For persistence, it drops a copy of itself into an application-data folder and creates a registry startup entry — both named using eight-character hexadecimal strings derived from the system’s own volume information, making each infection’s artifacts look slightly different from the next. The malware even tampers with Windows’ startup-approval settings specifically to stop users from disabling the autorun entry through Task Manager.
From there, the injected downloader pulls encrypted shellcode over HTTPS, verifies a digital signature and checksum before running anything, and then executes the final payload entirely in memory using one of three methods: process injection, launching a standalone executable, or running a downloaded DLL directly.
Why Removable Drives Still Matter
This case is a pointed reminder that old-school malware distribution methods haven’t disappeared just because they’re unfashionable. Security teams should not assume that USB-borne threats are a solved problem from a bygone era. Organizations are advised to maintain active scanning of removable media at the endpoint level, watch for unusual registry startup entries and injected processes tied to common system utilities, and ensure endpoint detection tools are tuned to catch GPU-based decryption behavior rather than relying solely on CPU-based sandbox analysis, which this malware family is specifically designed to slip past.
Leave a Reply
You must be logged in to post a comment.