As reported by The Hacker News, Kaspersky has published analysis of a new CoffeeLoader variant distributed via the Retadup worm — a threat that French law enforcement reportedly disrupted seven years ago. The reappearance of infrastructure previously thought neutralized is a reminder that operational takedowns rarely erase the underlying code, developer knowledge, or distribution channels that keep malware families alive.
Why This Resurgence Matters
The cybersecurity community has a tendency to treat law enforcement actions as permanent victories. They are not. Retadup's return illustrates a recurring pattern: when threat actors retain source code, builder tools, or distribution networks, they can resurrect campaigns months or years after a coordinated disruption. The original 2019 takedown neutralized active C2 infrastructure but could not reclaim the worm's self-propagation mechanism or the human capital behind it.
For defenders, this means threat intelligence ageing assumptions are dangerous. A worm declared "dead" in 2019 should still appear in detection rules, endpoint hardening baselines, and incident response playbooks in 2026. The cost of maintaining detection for retired threats is trivial compared to the cost of rediscovering them during an active breach.
The GPU Decryption Evolution Is Worth Watching
The most technically notable shift in this CoffeeLoader variant is the packer's continued use of GPU resources for shellcode decryption — now migrating from OpenCL to OpenGL. This is not a novelty. GPU-based execution evasion is a deliberate response to endpoint detection and response (EDR) solutions that predominantly instrument CPU-side API calls and memory allocations. Most EDR agents do not have deep visibility into GPU compute contexts, making this an attractive evasion lane.
The shift from OpenCL to OpenGL suggests the actors are actively iterating to evade detection signatures built against the earlier variant — a sign of responsive, not static, adversary development.
Defenders should note that the packer hijacks legitimate Armoury Crate DLL naming conventions (“ArmouryAIOS.dll”, “ArmouryA.dll”) — a technique that blends malicious payloads with software associated with ASUS ROG systems. This social engineering of file names exploits analyst assumptions and can slip past allowlisting if organizations overly trust vendor-signed naming patterns.
Persistence and Injection: Familiar but Effective
The described persistence mechanism — copying a trojanized “7z.dll” to %PROGRAMDATA% or %LOCALAPPDATA%, establishing a Run key, and disabling user autorun controls — is technically unsophisticated but operationally effective. The use of legitimate process injection targets (dllhost.exe, WerFault.exe, svchost.exe, OpenWith.exe, AtBroker.exe) follows established loader tradecraft. These are processes that EDR solutions must carefully balance between behavioral alerting and operational noise — a balance attackers exploit.
Notably, the downloader creates a registry key to prevent users from disabling autorun via Task Manager. This is a low-level defensive circumvention that targets the human responder, not just the security tooling. It lengthens dwell time by frustrating incident response actions.
Shield53 Recommendations
7z.dll or similarly named library files appearing in %PROGRAMDATA% or %LOCALAPPDATA% subfolders with eight-hex-digit naming — a pattern inconsistent with legitimate software installation.rundll32.exe or system service hosts.7z.dll loaded via rundll32.exe from non-standard paths is a high-signal detection.The broader lesson: threat families do not die — they go dormant. CoffeeLoader's continued evolution, its link to SmokeLoader's codebase, and its use of Retadup distribution all suggest a mature, well-resourced ecosystem. Treat "resolved" threats as paused, not eliminated.