Guest Rivenmyst Posted January 21, 2009 Share Posted January 21, 2009 My Kaspersky Antivirus signals the presence of the trojan Trojan-Dropper.Win32.Small.cgh in the tool $OEM$, it's surely a false-positive.Could you verify and make it inactive at antivirus' control, please?Thanks in advance. Link to comment Share on other sites More sharing options...
Kelsenellenelvian Posted January 21, 2009 Share Posted January 21, 2009 You need to report it yourself at Kaspersky. Link to comment Share on other sites More sharing options...
Guest Rivenmyst Posted January 21, 2009 Share Posted January 21, 2009 (edited) I can trust?Why you don't fix the problem so other users will haven't the same problem and prevents any doubt? Edited January 21, 2009 by Rivenmyst Link to comment Share on other sites More sharing options...
Kelsenellenelvian Posted January 22, 2009 Share Posted January 22, 2009 I can't fix the problem. It is the way it is compiled. I used Quick Batch File Compiler and they are compiled with no password. (We have nothing to hide)This problem crops up every now and then because QBFC uses a UPX style compression. Link to comment Share on other sites More sharing options...
freeAppz Posted January 28, 2009 Share Posted January 28, 2009 Interesting..I have the same problem with AVG 8.0/freeAppz Link to comment Share on other sites More sharing options...
Stoner81 Posted February 1, 2009 Share Posted February 1, 2009 Ive had a similar thing in the tool CDSwitch. NOD32 v3 says its some kind of trojan but since I dont use the tool im not to bothered really just thought you might like to know about it. Link to comment Share on other sites More sharing options...
rajesh.kumar Posted March 31, 2009 Share Posted March 31, 2009 FSecure finds Tools\TaskKillS.exe as Trojan:W32/Agent.JCF Link to comment Share on other sites More sharing options...
Kelsenellenelvian Posted March 31, 2009 Share Posted March 31, 2009 Like I said before they are false positives, compiled with older versions of auto-it. Link to comment Share on other sites More sharing options...
mritter Posted April 1, 2009 Share Posted April 1, 2009 If you update to the latest version of WPI you will no longer need TaskKill.exe. WPI does it internally now. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now