pdf
Feb 22 2004, 01:52 PM
ok I openned the file wlistbox.exe (it's found in some autohackers)
http://www.governmentsecurity.org/forum/in...t=0entry49036and it's a trojan! , it crashed my norton antivirus 2004!
I killed the trojan files and removed it but
when I reinstalled norton antivirus , I tried to scan my computer for viruses...
and it says something like "can't find some specifed files..."
(the trojan files was: "coco.exe" , "rundll16.exe")
I'm not sure if there are other files...
what can I do?
any ideas?
ducky
Feb 22 2004, 02:19 PM
try searching google for : " anti trojan"
you can find lots off softwares that will help you remove that trojan
pdf
Feb 22 2004, 02:25 PM
the trojan file name: "wlistbix.exe"
I tried google but I didn't find any solutions
I tried to read help about this problem but didn't work
http://service1.symantec.com/SUPPORT/nav.n...ocument&src=_mi
dragonfly
Feb 22 2004, 02:42 PM
go to www.download.com and download trojan remover or something
pdf
Feb 22 2004, 03:30 PM
I tried "trojan remover" but with no results (0 trojans found)
BertolamiD
Feb 22 2004, 03:52 PM
wlistbix.exe = tool used by hackers , it isn't a trojan just because norton says so.
F:\tools\test>wlistbix
Usage: wlist.exe <ip-liste> <batch-datei>
means, :
you need an IP list, and a batchfile with commands in it I'll show you all how it works.
| CODE |
F:\tools\test>echo start exploit.exe %1 8080 >> test.bat
F:\tools\test>wlistbix list.txt test.bat
F:\tools\test>start exploit.exe 10.0.0.1 8080 The system cannot find the file exploit.exe.
F:\tools\test>start exploit.exe 10.0.0.2 8080 The system cannot find the file exploit.exe.
F:\tools\test>start exploit.exe 10.0.0.3 8080 The system cannot find the file exploit.exe.
F:\tools\test>start exploit.exe 8080 The system cannot find the file exploit.exe. Done. |
btw, if you can't remove it or find it, it might mean it's allready gone, and you 're just having troubles with your PC , format c:\ and clean install to make sure of any other files you don't want on your PC..
pdf
Feb 22 2004, 04:14 PM
mm i think i will format my C :|
I don't have other options now , I also checked security "symantec security" and see that my computer still infected with 4 trojans (I think it's duplicated)
ok thnx all for the help
xzibit
Feb 22 2004, 04:30 PM
i play with trojans a lot for testing purposes and whatnot. this is how i give them the quickfix. Go to start<run< type msconfig. Go to startup and uncheck any unfamiliar/weird looking programs. These are the programs that execute upon boot up. Just uncheck then reboot and u should be safe. The trojan may still be floating around on ur HD, but at least u know its not running
MxMx
Feb 22 2004, 05:01 PM
damn

..
restart in safe-mode .. than virusscan and remove that damn thing
TwitcH
Feb 22 2004, 09:01 PM
could try blockin the port the trojan is using from incoming connections??
pdf
Feb 22 2004, 09:16 PM
I successfully removed the trojan

it seems undetectable by anti viruses
It has been hiding in temp directory

, I used WINBRUSH to clean all the damn things and stopped some services
TwitcH
Feb 22 2004, 09:35 PM
Congrats
Richie
Feb 23 2004, 07:41 AM
I'd say the easiest way to remove some of the sneakier trojans is to just download the client and try to connect to yourself, assuming you know which trojan you have of course. Just bruteforce your way in, or hope there's no password.
chris105
Feb 23 2004, 08:47 PM
| QUOTE (xzibit @ Feb 22 2004, 04:30 PM) |
| i play with trojans a lot for testing purposes and whatnot. this is how i give them the quickfix. Go to start<run< type msconfig. Go to startup and uncheck any unfamiliar/weird looking programs. These are the programs that execute upon boot up. Just uncheck then reboot and u should be safe. The trojan may still be floating around on ur HD, but at least u know its not running |
Im afraid that that is not true, trojans can use multiple ways to start up like the registry for example
chris105
Feb 23 2004, 08:48 PM
| QUOTE (pdf @ Feb 22 2004, 09:16 PM) |
I successfully removed the trojan it seems undetectable by anti viruses
It has been hiding in temp directory , I used WINBRUSH to clean all the damn things and stopped some services |
Chances are its just a standard trojan packed up or hex-edited
chris105
Feb 23 2004, 08:49 PM
| QUOTE (Richie @ Feb 23 2004, 07:41 AM) |
| I'd say the easiest way to remove some of the sneakier trojans is to just download the client and try to connect to yourself, assuming you know which trojan you have of course. Just bruteforce your way in, or hope there's no password. |
Sorry mate complete bullshit.
pdf
Feb 23 2004, 09:02 PM
chris105 yeah it was a trojan that also 'infected' the registery files (when I cleaned the registery files of the trojan files it's completly removed from my pc) (it was also in the norton-symantec registery keys)
Richie
Feb 29 2004, 08:10 PM
| QUOTE (chris105 @ Feb 23 2004, 02:49 PM) |
| Sorry mate complete bullshit. |
Care to elaborate? Your opinion seems more valid when you give reasons.
usch
Feb 29 2004, 08:22 PM
let me try that.if you know which trojan it is u can just use google and look for a fix.shouldn`t be that hard
Richie
Feb 29 2004, 10:23 PM
Often, the fixes for the trojans involve more time than just clicking "remove". Of course, I have yet to encounter someone who has put a password on their server.
Black Flag
Mar 1 2004, 12:21 AM
the cleaner from moosoft worms well.
search for it.
xzibit
Mar 1 2004, 02:58 AM
| QUOTE (chris105 @ Feb 23 2004, 08:47 PM) |
| QUOTE (xzibit @ Feb 22 2004, 04:30 PM) | | i play with trojans a lot for testing purposes and whatnot. this is how i give them the quickfix. Go to start<run< type msconfig. Go to startup and uncheck any unfamiliar/weird looking programs. These are the programs that execute upon boot up. Just uncheck then reboot and u should be safe. The trojan may still be floating around on ur HD, but at least u know its not running |
Im afraid that that is not true, trojans can use multiple ways to start up like the registry for example
|
ah true but most of the time if they use the registry they will show up in startup in msconfig
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.