Share this post

Link to post

Share on other sites

EBak 0

Thanx for all the answers. The problem is fixed for now, by getting a new update of McAfee or the newest beta version of AutoIT. I updated both the programs at the same time, so I am not sure which one is responsible for it. Hopefully it stays like this. I only lost all backup executables, but i can still compile them with the newest AutoIt version if I need them.

Share this post

Link to post

Share on other sites

flaxcrack 0

Since the update of Mcafee on 3 March 2006 all my executables that I did create with AutoIt are detected as a virus/Joke. Is anyone else has this problem and what can I do about it?

regards,

Emile

Yep, I get that even with some of my .au3 files.

[quote] Gilbertson's Law: Nothing is foolproof to a sufficiently talented fool.Sandro Alvares: Flaxcrack is please not noob! i can report you is stop stupid. The Post[/quote]I made this: FWD & MD5PWD()

Share this post

Link to post

Share on other sites

flaxcrack 0

I cannot understand and antivirus detecting a virus in a pure text file.

Nope...just on the .au3 file itself. The next time McAfee picks it up i'll paste the message in here.

[quote] Gilbertson's Law: Nothing is foolproof to a sufficiently talented fool.Sandro Alvares: Flaxcrack is please not noob! i can report you is stop stupid. The Post[/quote]I made this: FWD & MD5PWD()

Share this post

Link to post

Share on other sites

wizzardking 0

Post an example so we can check to see if other virus scanners also note it as a virus.

AVG also returns with a virus report for autoit, however not just on what I have compiled but also for the autoit executable itself. I actually had to turn off autoprotect to get it to stop poping up warning messages on my server. I thought it was a bad install of AVG professional guess not eh?

Also after reading these posts I installed autoit on my norton corp edition protected server, and it also says it's a virus BUT windowsonecare and ms defender do not, and Avast! doesn't either. with norton I just created an exclusion, and wrote AVG about it not being a virus and the fact that thier exclusion doesn't stop the stupid popup warnings every 5 seconds.

`Mitch

Share this post

Link to post

Share on other sites

jpm 38

AVG also returns with a virus report for autoit, however not just on what I have compiled but also for the autoit executable itself. I actually had to turn off autoprotect to get it to stop poping up warning messages on my server. I thought it was a bad install of AVG professional guess not eh?

Also after reading these posts I installed autoit on my norton corp edition protected server, and it also says it's a virus BUT windowsonecare and ms defender do not, and Avast! doesn't either. with norton I just created an exclusion, and wrote AVG about it not being a virus and the fact that thier exclusion doesn't stop the stupid popup warnings every 5 seconds.

`Mitch

I can agree an antivirus can give in this specific case a lase alarm if your machine is not infected on the autoit executable or a compiled script which is build from the same code.

But giving and alarm on an script itself (.au3) which is a text file is beyond my comprehension except this test file that Mc Afee distribute to check if their code is detecting something.

As usual I have no answer of which version of autoit produce this 'false" alarm.

The best is to forward your file to your antivirus provider and have them correct their detectection algorithm/signature.

Share this post

Link to post

Share on other sites

Confuzzled 1

Could we make a common thread, title it "My anti-virus just called AutoIT badware" or something similar, sticky it, and move all these posts that keep cropping up on a daily/weekly basis into them? This would be an ongoing, long and sad reflection on the quality of anti-virus signature algorithms. Noobies could (possibly) see it before starting their own thread.

I've had widely deployed compiled scripts disappear overnight on more than one occasion - one of the hazards of using a popular product that has too much power I suppose. Where anti-virus vendors are lazy to differentiate between valid nasties and the common non-infested runtime, having a common thread will document that on an ongoing basis.

(Could be worse - it could be McAfee reporting and deleting Excel.exe like happened last Friday I suppose)