[quote name=‹ supranico › date=’ 19 Feb 2005, 02:05’]A propos de spyware bien gonflant, j’ai du passer au formatage de mon HD à cause d’un
certain VX2…
En surfant sur des forums hardware sur le net, j’ai chopé un moyen de le virer en 12 ou 13 étapes
Bon, j’ai préféré formater.
A priori, aucun logiciel ne peut faire sauter ce VX2 , même le soit-disant VX2-cleaner de Ad-aware SE…
Je pense sans doute ne pas être le seul à avoir chopé ce schmut…
[right][post=« 334126 »]<{POST_SNAPBACK}>[/post][/right][/quote]
Je déterre ce thread parce que c’est ce que j’ai… Une variante du VX2 et aucun, aucun soft ne parvient à le virer.
J’ai pas de pop-ups gonflant, juste une toolbar sans nom quand je fais hijackthis, ainsi qu’un plantage de msn (ça c’est depuis que je trifouille la base de registre) au lancement, mais surtout un plantage d’explorer en quittant. Je me suis replongé dans l’extermination de cet abruti car il me pourri ma barre des tâches qui fonctionne mal. C’est un vieux truc d’il ya des mois et il est toujours là. Chuis vert.
J’ai tout essayé, tout les antispyware et antivirus que je pouvais. Pour tous ou presque (le scan online de Panda me dit que je suis infecté), je suis clean. Les modes sans echec et les reboot sont inutiles, le lascard a les droits d’admin et fait ce qu’il veut. En même temps ça fait gagner du temps
J’ai trouvé la méthode en 12/13 étapes, je l’ai exécuté mais apparemment c’est une vrai saloperie le truc; j’arrive pas à localiser le process lançé. Un moment il utilisais rundll.exe c’était relativement facile de le chopper, là je le soupçonne de se cacher, peut-être sous msn (que j’ai retiré du démarrage et qui revient). Depuis rundll.exe n’est plus exécuté mais j’ai pas confiance… Je vais refaire un scan Panda.
L’analyse de log me permet de voir que tout les process lançés d’explorer, sont signés xpsp_sp2… Une variante de ce vers aurais t-elle réussi à se faire passer pour un process authentifié ?
Voilà en fait ma question
Je colle la méthode qui fait quand même bien le ménage.
[code]VX2 does the following to your system:
- can create the file c:\windows\system32\guard.tmp
- also creates random .dll files in c:\windows\system32
-fortunately they are the same file size and will have
todays date so they’re easy to spot
- upon shutdown, rebooting will generate new random .dll files
-it uses only 1 random .dll file at a time, it will create an
extra one that will become the new .dll file to be used by
RunDll32.exe on the next boot. When you reboot, another .dll file
is created for when you reboot again. See how sneaky it is.
- Look in processes and you will see RunDll32.exe running
-hit ctrl + alt + delete and click processes to look for it
-You can end the RunDll32.exe process but it will come back, over
and over
- attaches itself to the winlogon process used by windows
-therefore can run in safe mode as well, doh!
- Pops up spyware windows occasionally from the RunDll32.exe process
Software you will need. Do a search online for these:
- VX2Finder.exe
- Hijackthis
- Process Viewer (http://downloads.subratam.org/pv.zip)
- Killbox.exe
- Ad-Aware SE
- Spybot
- CWShredder
Here is the trick to removing this nasty spyware.
- run the runme.bat file in the Process Viewer folder
-should be located on the Tech Bench Tools cd in sftw fixes\spyware.
-use option 5, a log file should be created in notepad. Next use
option3. You should have two logfiles opened.
-look through these log files for any entries that do not have the
words « xp » out to the far right. exclude COMRes.dll,OLEAUT32.dll,CLBCATQ.dll,
or any others that tell you exactly who the publisher is.
- Now that you have the proper files pinpointed, run killbox.exe
-should be located on the Tech Bench Tools cd in sftw fixes\spyware.
Copy/paste the location of the file into the text input box. Select the option to delete on reboot. Hit yes when prompted if ok to delete, but hit no when asked to reboot. Repeat this for all other suspected files.
-
navigate to c:\windows and delete the file named wininit.ini if it
exists.
-This is commonly used by spyware to rename itself upon windows
restarting. Windows also uses it for its own purposes as well.
Don’t worry, when windows needs it, it will recreate the file.
-
Run Hijack This and delete any suspected entries
-
Now reboot your computer and boot back in regular mode again
-
If you did it correctly, you should not get any errors upon booting
in windows. Also, RunDll32.exe should not be running in
processes(double check this).
-
Next, navigate to c:\windows\system32 and in the view menu choose
detailed view. Choose to arrange icons by date modified. Look for todays or
yesterdays date. Look for any random .dll files around these dates that should
all be around the same file size. There could even be some that are before
yesterdays date if the machine has been infected long enough. To be
safe stick with todays date and yesterday. DO NOT DELETE WPA.DBL, this is
the windows product activation database (WPA) file. It has a tendency to
have a current date modified. Only delete the proper .dll files.
-
Clear all temp folders. There is a clear_temp_files.bat file on the
Tech Bench Tools cd in sftw fixes\spyware
-
Run the VX2Finder.exe app and run a scan. Click on the « Open regedit » button.
Click on each key and on the right look at the DllName entry, look
for a random .dll name. Google a dll if you are unsure. Delete the key on the left
if any suspecting keys are found. Back to the VX2Finder app, click each of
the 3 buttons on the right labeled « Restore Policy », « User Agent$ », « Guardian
.reg » but choose not to restart computer.
-
Run a winsock fix to reset the hosts file, your machine should restart at this point.
-
Now run Ad-Aware SE, Spybot, Hijack This, CWShredder, and BHODemon
-
Double check in msconfig for any bad entries and run asviewer.exe
(located on Tech Bench Tools cd in misc\Startup Viewer). Delete any suspicious
entries.
-
reboot computer final time, all should be done .
You should be clean of VX2 now. This has got to be the hardest spyware
ever to remove because it attaches itself to the winlogon process and in the Notify key in the registry.[/code]
Non je ne veux pas réinstaller. Pas encore B)