A Takedown That Didn't Stick
In 2019, French law enforcement and Avast coordinated one of the more celebrated botnet takedowns of the decade, sinkholing the command-and-control infrastructure behind Retadup, a worm that had infected hundreds of thousands of machines — largely in Latin America — and was being used to mine cryptocurrency and spread other threats. Seven years later, Retadup is back in the news.
According to research published by Kaspersky and reported by The Hacker News, a new variant of the worm has resurfaced and is now being used as a distribution channel for CoffeeLoader, a malware family designed to deliver additional payloads onto infected systems.
The revival is a reminder that sinkholing infrastructure disrupts a campaign's operations but does not necessarily eradicate the underlying code — or the population of machines that never received a cleanup.
How the New Variant Executes
Kaspersky's analysis describes an NSIS-based installer as the entry point. On launch, the installer drops a file named 7z.dll into a temporary directory and executes it through rundll32.exe — a living-off-the-land technique that abuses a legitimate Windows binary to run malicious code while blending into normal system activity.
The dropped 7z.dll is not the genuine 7-Zip library. Kaspersky found it to be a patched version of the legitimate DLL, repurposed as a loader. This kind of DLL side-loading and patching is a well-established evasion pattern: security tooling and users alike are conditioned to trust signed or familiar library names, and the abuse of rundll32.exe adds another layer of apparent legitimacy.
From there, CoffeeLoader's role is to fetch and execute further payloads, making the initial infection a staging point rather than the end goal. That modular design gives operators flexibility — the same loader can serve ransomware, infostealers, or proxyware depending on what the operator chooses to push.
Why Old Worms Keep Coming Back
The Retadup case illustrates a structural problem in botnet remediation. When a sinkhole is deployed, infected hosts that attempt to contact the seized domain are typically redirected to a disinfecting payload. The effectiveness of that approach depends entirely on hosts actually checking in. Machines that were powered off, offline, or behind restrictive network configurations during the takedown window may never have received the cleanup.
Those survivors form a dormant reservoir. Years later, a new actor — or the original operators — can reactivate the code, update the C2 logic, and rebuild distribution on top of an existing install base without needing a fresh exploitation campaign.
This is not unique to Retadup. Similar resurgences have been observed with other disrupted botnets, where portions of the infected population persist long after public reporting declares the threat neutralized. The lesson for defenders is that takedown announcements are not remediation events for their own environments.
Defensive Considerations
Several practical takeaways emerge from the technical details:
- Monitor
rundll32.exebehavior. Legitimate use ofrundll32.exeis common, but execution of a DLL from a temporary directory is a strong anomaly signal. Endpoint detection rules should flag this pattern, particularly when the DLL name mimics a well-known library such as7z.dll. - Scrutinize NSIS installers. NSIS is a widely used, legitimate installer framework, which makes it attractive to attackers. Correlating installer execution with subsequent child processes — especially
rundll32.exe— can surface abuse. - Treat legacy infections as live risk. Organizations should not assume that worms disrupted years ago are gone from their estates. Periodic hunting for known Retadup indicators and residual persistence mechanisms remains worthwhile, particularly in environments with long-lived or poorly inventoried endpoints.
- Watch for loader staging. CoffeeLoader's purpose is to bring in more malware. Detection should focus not only on the loader itself but on the network callouts and follow-on process activity that indicate a second stage is being retrieved.
The Bigger Picture
The Retadup revival underscores how the economics of malware favor reuse. Rebuilding a distribution network is expensive; resurrecting dormant code and an existing infected population is comparatively cheap. For defenders, the implication is that historical threat intelligence retains operational value long after a campaign has been publicly declared dead.
Kaspersky's full technical analysis provides the indicators and behavioral details needed to hunt for this variant. Organizations that documented Retadup activity during the original outbreak — and retained those detections — are well positioned to detect the new wave.
Source: The Hacker News — Retadup Worm Resurfaces 7 Years After Takedown to Spread CoffeeLoader Malware