Sign in to follow this  
Followers 0
Mungo

Error re alleged trojan in the AutoItSC.bin

4 posts in this topic

I tried to compile my script and my AV (f-prot) all of a sudden suggested a Trojan in the AutoItSC.bin. Reinstalled but still the same. Well, I believe it is most likely a false positive but haven't received a response from the AV vendor yet. I wonder, what could be in that file what could triggers that error - or are all compilers generally suspicious?

Thanks

Mungo

Share this post


Link to post
Share on other sites



http://www.autoitscript.com/forum/index.php?showtopic=34658


George

Question about decompiling code? Read the decompiling FAQ and don't bother posting the question in the forums.

Be sure to read and follow the forum rules. -AKA the AutoIt Reading and Comprehension Skills test.***

The PCRE (Regular Expression) ToolKit for AutoIT - (Updated Oct 20, 2011 ver:3.0.1.13) - Please update your current version before filing any bug reports. The installer now includes both 32 and 64 bit versions. No change in version number.

Visit my Blog .. currently not active but it will soon be resplendent with news and views. Also please remove any links you may have to my website. it is soon to be closed and replaced with something else.

"Old age and treachery will always overcome youth and skill!"

Share this post


Link to post
Share on other sites

Thanks for the link to the above page - sorry, haven't detected it before. The warning is actually triggered during compilation and related to AutoItSC.bin. The AV stops the compilation. I can run code I compiled a few days ago (earlier version of my script).

Thanks

Share this post


Link to post
Share on other sites

Thanks for the link to the above page - sorry, haven't detected it before. The warning is actually triggered during compilation and related to AutoItSC.bin. The AV stops the compilation. I can run code I compiled a few days ago (earlier version of my script).

Thanks

Just as a short feedback. F-Prot confirmed false positive.

"this is a false positive and it will be fixed in the next signature update.

Thanks for notifying us.

We apologize for any inconvenience caused by this."

Share this post


Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0