Trojan:W32/Vundo is a large family of trojans closely associated with adware program that downloads and displays pop-up advertisements.
Based on the settings of your F-Secure security product, it will either automatically delete, quarantine or rename the detected program or file, or ask you for a desired action.
Find the latest advice in our Community Knowledge Base.
See the manual for your F-Secure product on the Help Center.
Submit a file or URL for further analysis.
The adware is normally downloaded by users from the websites; these malicious sites are normally promoted by spam emails. The Vundo family is often distributed as DLL files. It is known to be bundled with adware and/or spyware programs.
For representative examples of Vundo variants and associated programs:
Malware in the Vundo family are installed without the user's consent as a Browser Helper Objects (BHOs). During installation, the DLL file is dropped in Windows system directory. The file name is randomly generated using 8 alphabetic characters:
Upon execution, the DLL is injected into 2 running processes:
In some variants, several data files are created in the same location as the DLL file's execution. The data files' attributes are set as system file and hidden. The files use random names and the following extensions:
Once installed, the trojan modifies Microsoft Internet Explorer's security setting to trust cookie content created by the trojan:
Some variants may also attempt to download and execute arbitrary files from remote websites such as:
The program runs hidden from the user.
During installation, malware in the Vundo family create a registry launch point with a unique Class ID. This launch point automatically starts the DLL when system is restarted.
To find this launch point, navigate to the following registry and look for the malicious file pointed by "InprocServer32" registry key:
The program will also make further modifications to load itself at startup:
For some variants, the following registry keys are also created to load the program whenever the user logs on or off. The keys will use the same DLL file name as its key: