|
|
#1
April 11th, 2002, 10:50 PM
|
|||
|
|||
js.seeker
When browsing Norton alerted me to the fact that it detected js.seeker. *I then scanned several times, with full updates, and found nothing. *WHat to do now?
|
|
#2
April 11th, 2002, 11:03 PM
|
||||
|
||||
|
Re: js.seeker
Hello Saruman,
Although you didn't mention the O/S installed, here's general info concerning js.seeker: http://vil.nai.com/vil/content/v_98882.htm Apart from that, there are several variants. Could well be - depending on how you configured Norton - it has been dealt with. Nevertheles, the log file should provide info. I presume you performed a deep scan, all files included? regards. paul
__________________
01110010 01100101 01100111 01100001 01110010 01100100 01110011 00100000 01110000 01100001 01110101 01101100 |
|
#3
April 12th, 2002, 01:03 PM
|
||||
|
||||
|
Re: js.seeker
What probably happened is, you visited a site that tried to infect you with the JS.seeker virus. It would then be in your browser cache. A good AV will stop js.seeker from infecting you and changing your home page, etc. but most of the time keeps detecting it in the cache and says it can't remove it. Clear the cache and it's gone.
In your case, either it was a false detection or somehow it did not end up in your cache. I have had it get as far as my cache a couple of times. No big deal.
__________________
"There is a principle which is a bar against all information, which is proof against all arguments and which cannot fail to keep a man (and a woman) in everlasting igonorance- that principle is: Contempt prior to Investigation." -Herbert Spencer |
| « Previous Thread | Next Thread » |
| Thread Tools | Search this Thread |
|
|
