View Full Version : LeakTests in bases
Owner
August 19th, 2007, 05:41 PM
Eset added leak tests in their base.
__http://www.eset.eu/podpora/aktualizacia-2469?lng=en
__http://www.eset.eu/podpora/aktualizacia-2470?lng=en
Hm.. why? ;)
flyrfan111
August 19th, 2007, 05:44 PM
Yes, it is strange. I thought they only liked to add TRULY malicious stuff.
PcBorg
August 19th, 2007, 09:03 PM
thats interesting... maybe its so ESS seems to pass those tests? Havent checked the bases by the way... peace
The Hammer
August 19th, 2007, 10:06 PM
{QUOTE-> thats interesting... maybe its so ESS seems to pass those tests? Havent checked the bases by the way... peace <-QUOTE}Interesting naming of malware perhaps. But doubt you or the Owner are correct. I absolutely do not believe it's an attempt to cheat.
flyrfan111
August 19th, 2007, 10:15 PM
{QUOTE-> Interesting naming of malware perhaps. But doubt you or the Owner are correct. I absolutely do not believe it's an attempt to cheat. <-QUOTE}
Nope, common named firewall tests,
Win32/Leaktest.AWFT, Win32/Leaktest.CopyCat (2), Win32/Leaktest.Ghost (2), Win32/Leaktest.PCAudit (3), Win32/Leaktest.Thermite, Win32/Leaktest.WallBreaker (2), Win32/Leaktest.Yalta
flyrfan111
August 20th, 2007, 05:17 AM
Just a guess, but perhaps it could be a basis for heuristic detections of malware using the same techniques that leak tests are using.
ASpace
August 20th, 2007, 08:36 AM
They are detected as potentially unwanted programs
From NOD32 v2 's Help file:
{QUOTE-> Potentially unwanted applications are programs that might not actually pose a security risk; these applications usually require a user's consent before installation. They may affect your system's behavior in the following ways:
a) showing windows that would normally not open
b) activation and running of processes hidden to the user
c) increased consumption of system resources
d) change of search results
e) communication with the application provider servers <-QUOTE}
flyrfan111
August 20th, 2007, 02:17 PM
{QUOTE-> They are detected as potentially unwanted programs
From NOD32 v2 's Help file: <-QUOTE}
Doh, Thanks HiTech, didn't think of that.
Marcos
August 20th, 2007, 02:21 PM
{QUOTE-> Just a guess, but perhaps it could be a basis for heuristic detections of malware using the same techniques that leak tests are using. <-QUOTE}
That's right.
ugly
August 20th, 2007, 02:23 PM
This is what matousec said about that :
" The sad and funny thing in once is that lots of them mark leak-testing software as viruses or malware. The better engines mark leak-testing software only as potentially unwanted software, which is much better, but still it seems that these products worry about leak-tests. Why? To perform our tests against these products we had to switch antivirus engines of such products off to get real results of their anti-leak protection. Such behaviour can be also marked as cheating on leak-tests."
NOD32 user
August 20th, 2007, 02:28 PM
{QUOTE-> ...The better engines mark leak-testing software only as potentially unwanted software, which is much better, ... <-QUOTE}Almost sounds like they have quoted from the NOD32 help file :)
Cheers :)
solcroft
August 20th, 2007, 06:54 PM
{QUOTE-> They are detected as potentially unwanted programs
From NOD32 v2 's Help file: <-QUOTE}
If that's the case, then I'd suggest ESET come up with a better naming convention for them, Avira's SPR/xxx or Kaspersky's not-a-virus:xxx for instance. Simply by looking at the names, there's no way of telling whether NOD32 is trying to mark them as PUPs or malicious trojans, and the suspicion of ESET trying to cheat their way through in leaktests will weigh heavily indeed.
flyrfan111
August 20th, 2007, 07:15 PM
Read Marcos' (post 9) response to my guess.
Marcos
August 21st, 2007, 01:03 AM
{QUOTE-> If that's the case, then I'd suggest ESET come up with a better naming convention for them, Avira's SPR/xxx or Kaspersky's not-a-virus:xxx for instance. Simply by looking at the names, there's no way of telling whether NOD32 is trying to mark them as PUPs or malicious trojans, and the suspicion of ESET trying to cheat their way through in leaktests will weigh heavily indeed. <-QUOTE}
PUA's are called applications. Read my post, it's not just detection of the leak tests, it's a generic detection for malware that exploits the same "holes" as the tests do.
solcroft
August 21st, 2007, 01:19 AM
{QUOTE-> PUA's are called applications. Read my post, it's not just detection of the leak tests, it's a generic detection for malware that exploits the same "holes" as the tests do. <-QUOTE}
I've already read it. All I'm saying is that for people who haven't, the suspicion will be there, since it's not obvious at all that NOD32 is flagging them as PUAs.
flyrfan111
August 21st, 2007, 01:25 AM
{QUOTE-> I've already read it. All I'm saying is that for people who haven't, the suspicion will be there, since it's not obvious at all that NOD32 is flagging them as PUAs. <-QUOTE}
I have to concur, my initial reaction was WTH, then I thought about it and realized the generic/heuristic detection idea. A different naming scheme might avoid accusations.
alant
September 1st, 2007, 12:38 PM
I recently installed McAfee security Center and it flagged Demo-leak test that I had previously installed as "potentially unwanted programs" (also got the message: "McAfee attempted to disable the program but some parts could not be removed"). I tried to remove them with McAfee and it said they cannot be completely removed. I thought I'd just uninstall them myself and be done with it. I can't find them in Programs or Add/Remove programs. The exec files are in a download folder I have. Would deleting the files take care of the problem? Or are they really deeply embedded somewhere?
On another note, FindKeyXP caused the same message. Should I somehow allow McAfee to ignore these?
Thanks, Alan
vBulletin® Copyright ©2000-2009, Jelsoft Enterprises Ltd.
Copyright ©2002 - 2009, Wilders Security Forums