last update Sentinel Win32/Adware.LastDefender application

Hi
i downloaded the last version of sentinel http://www.runtimeware.com/products_home.html

well nod32 detect it like setup.exe - Win32/Adware.LastDefender application

is a false allarm or is there a adware inside?

thanks

 

I'm having the same issue with several known good exe's and have a call into support. I have a feeling it's false positives and an issue with update 3034.

 

SERIOUS ISSUE!!!

Multiple installed applications have been dumped into Quarantine on multiple known machines! This includes, but is not limited to:
eyebeam, PRTG traffic grapher, nmap, ultravnc

Recent definitions are FLAWED!

 

Just had ROHOS_MINI.EXE deleted (quarantined).

The reported threat was 'Win32/Adware.LastDefender application' detected with the definition file 3034 (20080417)


Rohos: http://www.rohos.com/free-encryption/

Very useful utility as it does not require administrative rights on the client and, even more importantly, it is free. I downloaded the file a few weeks ago and I'll confess I've been hesitant to trust it due to the lack of peer review so I am not sure if this is a false positive or a vindication of my paranoia!

 

An update with a fix will be released shortly.

 

On my PC it detected the same "infection" in HTTrack Website Copier, All Phones Data Suite (Czech communication SW for mobile phones), Gothic 1 game, PDF Password Remover, some graphic card utilities and several others. I believe that it is false positive, hope that Eset will release fixed update soon, preferably with some official explanation.

 

4/17/2008 12:37:21 PM Real-time file system protection file C:\Documents and Settings\Steven Yevchak\Desktop\pg2-050918-nt.exe Win32/Adware.LastDefender application cleaned by deleting - quarantined NT AUTHORITY\SYSTEM Event occurred during an attempt to access the file by the application: C:\WINDOWS\Explorer.EXE.

Guess we all know which one THAT is!

 

The update 3035 with a fix for this problem has just been released.

 

I just got the 3035 update... hopefully will take care of this. Very lucky here that it was mainly my system that was affected. I can't imagine having to restore files from quarantine on 100's of machines.

 

Add XviD-1.1.0-30122005.exe to the list, using update 3035. File has been submitted to Eset for further analysis.

Is this your way of telling me that I should update to XviD 1.1.3?

***EDIT***
It turns out that the XviD file was caught by 3034, but NOD32 updated to 3035 three minutes later. In other words, 3034 *was* the problem. I have restored the file with 3035, and it seems to work just fine now.

Thanks for correcting the problem, Marcos and everyone else at Eset.

 

Can I ask what the cause of the problem was? (just curious how it'd pick up so many unrelated instances)