Researchers documented Opachki as a Russian-focused trojan that arrived through a dropper, installed a malicious DLL, and used packers including Mystic Compressor and UPX to complicate analysis and removal. The malware disabled Windows Safe Mode by deleting the SafeBoot registry key, checked infected hosts for Zeus components, and in some cases renamed Zeus-related files, suggesting it competed with or attempted to take over systems already compromised by other banking malware. Public sample reporting later tied the campaign to a dropper and dropped DLL widely detected by antivirus vendors as Opachki or related packed trojan families.
The trojan’s core capability was to hook Windows networking functions in memory, including recv(), WSARecv(), WSASend(), and send(), allowing it to intercept traffic for ports 21, 25, 80, and 110 and steal credentials from FTP, web, and email sessions. It also hooked browsers such as Firefox, Internet Explorer, and Opera, as well as the Russian ICQ client QIP, then injected malicious JavaScript into web responses to redirect victims through attacker-controlled infrastructure, hijack links, and capture search queries—particularly when users arrived from search engines, enabling Google-style redirection fraud and traffic monetization.

Pull IOCs and campaign context straight into your stack.
6 events from the most recent confirmed update back to the earliest known activity.
Contagio published an update on Opachki that shared the dropper.exe and rundll32.dll sample hashes and linked the sample to prior public reporting on Opachki's web-link hijacking and Google redirections. The post noted that newer variants might have lower detection rates and slightly different names.
The dropped Opachki payload rundll32.dll was submitted to VirusTotal and also detected by 37 of 42 antivirus engines. Microsoft, McAfee, and NOD32 identified the DLL as Opachki or a closely related variant.
The Opachki dropper.exe sample was submitted to VirusTotal, where it was detected by 37 of 42 antivirus engines. Vendors including Microsoft, McAfee, and Trend Micro classified it as Opachki or a related trojan family.
A SANS ISC diary analyzed Opachki as an actively spreading link-hijacking trojan that disabled Safe Mode, hooked browser and QIP network APIs, injected malicious JavaScript into web responses, and redirected users through attacker-controlled infrastructure. The report also noted Opachki checked for Zeus infections and renamed Zeus-related files, suggesting competition for infected hosts.
A later Contagio post stated that an Opachki sample consisting of dropper.exe and a dropped rundll32.dll dated to October 2009. The sample was identified as part of the Opachki link-hijacking trojan family.
A Habr analysis described the malicious DLL ftp34.dll, a descendant of an earlier trojan, detailing how it hooked Windows socket APIs to intercept traffic on ports associated with email, web, and FTP sessions. The write-up documented inline hooks on recv(), WSARecv(), WSASend(), and send(), indicating theft of credentials directly from network traffic.
Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.
Indicator values are masked on this page. View all 16 in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.
Pull the IOCs, campaigns, and victimology behind this family, ready to push into your SIEM and EDR.
4 references tracked. Mallory keeps watching after this page renders.
contagiodump.blogspot.com
Open sourceisc.sans.edu
Open sourcecontagiodump.blogspot.com
Open sourcehabr.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.