NS Keylogger in Spywareblaster?

Hi,

If there is an "un-quarantine" option in Microsoft Anti-Spyware, that will probably work instead of you having to install SpywareBlaster again over-the-top.

If Microsoft Anti-Spyware then falsely detects the file again (which it probably will), you should definitely ignore it (at least until they fix the false-positive).

I hope this helps.

Best regards,

-Javacool

 

Thanks for prompt reply - there is an option to undo quarantined item in MS AntiSpyware, so that is easy. I believe it will continue to be reported until MS corrects their problem. Really sorry about that part - know you are too - it's just part of a Beta program, I guess. Thanks again.

 

Thanks javacool, I'm sure you've set many minds at rest with your quick response.....

 

As noted in a closed thread from yesterday....before this thread was started....I did not receive this False Positive with version 5709. I have been told that the latest 5711 version is supposed to have fixed this problem. Perhaps those that are receiving this False Positive can download the update and perform a scan to see if indeed it's fixed

 

Just got update 5711 (took forever to download), but does not, I repeat, does NOT fix the false positive.

Acadia

 

Do you have the latest build of MSAS beta (1.0.509)?

With that build and def 5711, unins000.exe is no longer flagged on my system XP SP2 (it was with 5709)

With earlier build people report it as still being flagged:

http://forums.net-integration.net/index.php?showtopic=30065

 

Oh well it initially did not effect some(some Win2K users that is)....then the latest update fixed it for some....but not all. Surely they will get it right sooner than later

 

Thank you, JR, that appeared to be the problem, I did not even know that MS had updated the program version. Once I uninstalled the old, and installed 1.0.509, then installed the latest 5711, all is well, thanks again.

Acadia

 

For the record, I've just run MSA V5711 on XP Home SP1 - 'keylogger' is no longer identified.

 

Re: NS Keylogger in Spywareblaster? - FIXED!!!

It is fixed!!!!

Download the new Microsoft Anti-Spyware definitions file 5711 for April 23, 2005!

 

Could someone please confirm the unins000.exe file size?

Hi,

Im no longer getting the FP with the new MSAS rel 5711.

Just out of curiousity, could someone please confirm that the size of the unins000.exe for spywareblaster, is suppose to be a whopping 625Kb!

Thanks
Jack

 

Yup, mine is that large too!

Acadia

 

Well I blame it all on Bill Gates and his buggy microsoft company. maybe with great respect to javacol and there wonderfull software we all should Rattle
Bill Gates on this one.

 

dang i quarintined it grrrr am i screwed now? i didn't know it was from spywareblaster in the first place.

 

Looks like update 5711 has fixed the False positive: I updated Giant AS [Predecessor to MS-AS] to 5711 and checked 3 PC's - 2 XPSP2's and a 98SE [Where keylogger was detected with 5709]. None of the scans detected the NS Keylogger in Spywareblaster.

 

Hi Cheater,

No, Just un-quarantine it -or- reinstall SB 3.3 over top the existing program, which will replace the now missing uninstaller.

Steve

 

Thanks for all your responses and help, javacool. Things look fine again. Appreciate it.

 

After you reinstall SB 3.3 make sure you check it for updates.I had to do a reinstalled just now and when I checked for updates there were some..

Grand Dad

PS I did like a lot of others and when MS Antispyware showed a Keylogger didn't stop and look .

 

It happened to me. no need to re-install spywareblaster. I did this:u
Just copy and paste the "unins000.exe" in another place. now let M$ antyspyware to delete the original "unins000.exe". Put back the one you copied in the original folder. Run M$ antispyware.

 

I found the keylogger late last night 2:15 am, I deleted it. This morning after I booted up I did another scan...came up clean. Opened the file in Windows Explorer.... unins000.exe was back.

 

Hi Carver,

I am not sure what you mean when you say "unins000.exe was back". If you had Microsoft Anti-Spyware program delete the unins000.exe file in the SpwareBlaster folder, then I don't know how it would have come back. If you are meaning that you searched your hard drive for other unins000.exe files, then yes, you should find many as many other programs also use that file as their uninstaller. Example, I have just over 11 instances of unins000.exe - each one belonging to the individual programs I installed.

The one we are discussing in this thread is SpywareBlaster's unins000.exe - that one being the one that Microsoft Anti-spyware was falsely detecting as a keylogger. This has all been explained in this thread, which I hope you have read through carefully. If you do not have an unins000.exe in your SpywareBlaster folder, then you will have to reinstall SpywareBlaster overtop the existing installation in order to replace the file, as this file is needed if you ever have to uninstall the SpywareBlaster program.

Please read through this thread again, and also this one: False-positive detection by MS Anti-Spyware

Regards,

snap

 

Thanks, just wanted to make sure that such a small app, had such a large uninstaller file.

Found it odd, because apps much larger than spywareblaster have smaller unins000.exe on my system, typically just 75Kb!

Jack

 

I find that alot of programs use the same named file as thier uninstall file.
Is there a reason for this? why do they all use the same file name? and if so
alot of people would have this file on thier computers making it easy to be a
widespread event that would affect a multitude of users.

 

thanx i installed it and i hope everything is ok thanx for you help dude

 

Hi snap, I meant it was back in the spywareblaster folder, I don't know how it could comeback ether . Could it be that the MS Anti-spyware detected a false-positive, then it deleted the false-possitive. The GUI reads that I deleted 1 piece of spyware. I was hopeing somebody could explain how it is possible.