Rising AV-SpywareBlaster FP?

[dw426]

Hi guys, is anyone getting a warning about "backdoor-vanbot" from Rising whenever they try to update SpywareBlaster 4.1? I scanned the SpywareBlaster folder and nothing came up, but when I try to update I get the warning. The first time Rising quarantined it before I could catch it and it rendered SpywareBlaster dead, which required a reinstall. This time I allowed it because at no other time has this virus been detected by any other AV.

[acr1965]

I just now updated SD manually and got no such warning from RFW.

[dw426]

{QUOTE-> I just now updated SD manually and got no such warning from RFW. <-QUOTE}

Well that's weird. I took off Rising and went back to Avast and Threatfire, and they aren't reporting anything. Who knows.

[acr1965]

Sorry, I may has misspoken. I was speaking about Rising Firewall. But apparently the firewall does some sort of checksum verification on programs trying to make an outgoing connection.

[Mirin]

Just opening and closing SpywareBlaster triggers the warning.

[munckman]

Rising AntiVirus flags SpywareBlaster for me as well.

[javacool]

{QUOTE-> Rising AntiVirus flags SpywareBlaster for me as well. <-QUOTE}

Hi,

Could you please contact their support and report this false-positive? These problems usually get fixed faster when multiple customers report the problem.

Best regards and thanks,

-Javacool

[dw426]

{QUOTE-> Hi,

Could you please contact their support and report this false-positive? These problems usually get fixed faster when multiple customers report the problem.

Best regards and thanks,

-Javacool <-QUOTE}

No problem, will do.

[munckman]

Rising AntiVirus no longer flags SpywareBlaster for me.

[munckman]

Rising AntiVirus flags SpywareBlaster for me again.???

[ghodgson]

Hi, Spywareblaster used to trigger Rising Av with me too, I reported it to Rising 10 days ago and everything seems ok now.
Gordon

[munckman]

{QUOTE-> Hi, SpywareBlaster used to trigger Rising Av with me too, I reported it to Rising 10 days ago and everything seems ok now.
Gordon <-QUOTE}
I had thought it was resolved but:

Virus Name - Time - Active Process - Created File

Malicious Code 2008-07-11 13:14:23 D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE; D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE;
Malicious Code 2008-07-13 17:42:46 D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE; D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE;
Malicious Code 2008-07-13 18:34:55 D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE; D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE;
Malicious Code 2008-07-13 18:39:15 D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE; D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE;
Malicious Code 2008-07-13 18:47:09 D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE; D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE;
Malicious Code 2008-07-13 18:48:56 D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE; D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE;
Malicious Code 2008-07-13 20:51:55 D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE; D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE;
Malicious Code 2008-07-18 12:27:00 D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE; D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE;
Malicious Code 2008-07-23 11:02:09 D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE; D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE;
Malicious Code 2008-07-23 12:17:23 D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE; D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE;
Malicious Code 2008-07-23 12:17:33 D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE; D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE;
Malicious Code 2008-07-23 12:19:05 D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE; D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE;
Malicious Code 2008-07-23 12:46:38 D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE; D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE;
Malicious Code 2008-07-28 21:37:29 D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE; D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE;
Malicious Code 2008-07-29 21:02:39 D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE; D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE;
Malicious Code 2008-07-29 21:04:28 D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE; D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE;
Malicious Code 2008-08-01 07:50:02 D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE; D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE;
Malicious Code 2008-08-01 13:54:20 D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE; D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE;
Malicious Code 2008-08-01 21:04:34 D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE; D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE;
Malicious Code 2008-08-02 17:46:01 D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE; D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE;
Malicious Code 2008-08-03 16:42:41 D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE; D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE;
Malicious Code 2008-08-03 16:58:01 D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE; D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE;
Malicious Code 2008-08-07 19:57:12 D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE; D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE;
Malicious Code 2008-08-07 20:28:52 D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE; D:\PROGRAM FILES\SPYWAREBLASTER\SPYWAREBLASTER.EXE;

the Rising logs say otherwise. :doubt: and I can't seem to exclude it from Rising's detection.

[ghodgson]

Hi Munckman,
Whilst I am no expert with Rising, try adding Spywareblaster.exe to the A/D whitelist in Active defense, ie go to Active defense- then settings- you will be asked for a passcode check, then click on the Active defense at the top (baseball glove holding a ball) and you will see the whitelist button at bottom right--add it there. I also added it to application protection. It stopped the pop ups for me.
By the way there seems to be a gliche with rising in so far as it doesn't remember users choices when a popup occurs and you tick the 'remember this at next boot up ' box.
I also have Clamwin as a second on demand scanner and that picks up 2 rising .dll files as a trojan ! I have also informed Clamwin about that FP.

Regards Gordon

[munckman]

{QUOTE-> Hi Munckman,
Whilst I am no expert with Rising, try adding Spywareblaster.exe to the A/D whitelist in Active defense, ie go to Active defense- then settings- you will be asked for a passcode check, then click on the Active defense at the top (baseball glove holding a ball) and you will see the whitelist button at bottom right--add it there. I also added it to application protection. It stopped the pop ups for me.
By the way there seems to be a gliche with rising in so far as it doesn't remember users choices when a popup occurs and you tick the 'remember this at next boot up ' box. <-QUOTE}

Thanks Gordon,

That stopped Rising from quarantining SPYWAREBLASTER.exe.:thumb: But like you said the Rising slider that quickly appears at the bottom right reappears after rebooting even after ticking remember. At least SpywareBlaster is functional and the notification slider is only displayed for a brief period of time.

Thanks for pointing out about Rising not remembering across reboots on the slider. I think I even had it set up like this before but threw my hand in the air because of Rising not remembering. I just figured I didn't add the exception to the correct place. This is acceptable until SB is no longer Flagged. SB is the only program that is wrongly flagged for me.

Appreciate the info.;D

[ghodgson]

Hi Munckman,
Glad things have been sorted to a degree. Hopefully Rising will sort out Spywareblaster as a FP soon, (already contacted them about it) and also the 'not remembering' gliche.
Having said that Rising does seem to be a very good Av which runs very light, and it is only a beginner so plenty of scope for improving on things.

Cheers Gordon