FalconFour

Yea, we did it! Thanks to BrettF for the much-needed push we needed to get the topic the needed attention. Looks like it's getting removed from the detections until they figure out how to (properly) detect malware in AutoIt scripts

MBAM is actually the best software we've used. There are others, sure, but MBAM is very clean, efficient, and gets the job 100% done, at least 95% of the time. If MBAM runs, the system comes out the other side clean. So we use MBAM. It just gets to be a pain in the rear when MBAM keeps flagging my notification program - an AutoIt program that beeps the PC speaker when the scan completes - as malware itself. @BrettF: Thanks! Glad to see I'm not the only one

Maybe if you'd read the topic instead of skimming, you'd not only see that it was already reported, but that Malwarebytes refuses to change their stance on it. Not only that, but I did read that, and Malwarebytes is nowhere to be found in that staggering list of useless AV programs. So it can generally be assumed - also by the fact that Google has next to no information relating to "malwarebytes autoit" - that the current issue, which ONLY STARTED LESS THAN A MONTH AGO, is still undocumented. Also, I'm not reporting that "omg my script is infeacted?!?!?!?", I'm reporting that a commonly used AV program is false-detecting scripts, and something needs to be done to support AutoIt on the MBAM forums. Slow down, calm down, breathe a bit, then... maybe... go back and read OP?

I wanted to drop by and point out some goings-on with what is, in my opinion as a PC repair tech, the #1 malware removal solution, Malwarebytes' Anti-Malware, versus false detections of compiled AutoIt scripts. As of the definitions around the beginning of this month, Malwarebytes is now flagging nearly all compiled AutoIt EXEs as "BackDoor.Bifrost". The worst part about it is, they refuse to change their stance about detecting AutoIt executables as malware/PUPs. I haven't yet gotten a reply to my request for "reconsidering" this decision. It's a pretty bad deal, considering AutoIt is no different from any of the hundreds of other programming languages out there (BTW, congrats on that, AutoIt team! Excellent work on that). I wanted to bring this to the AutoIt community's attention, see what you all think of it. I'm just one person and it seems like I'm the only person that has a problem with AutoIt being blanketed with the "malware" definition. Maybe the AutoIt team can help the Malwarebytes team with the detection of malware written with AutoIt... instead of just calling it all malware!

That makes sense, but what if the menu isn't open? The same area of the screen is also occupied by the "Processes" tab, which is usually the first thing we click in Task Manager. It'd be kinda telling if the cursor jumped out of the way all the time

Okay, I'm an "intermediate" Autoit user, I've made some scripts that automate Windows customization, and one that navigates a script-proofed GUI based on colors and cursor clicks. Now, I kinda want to make something a little funny. I work at a PC repair shop, and one of my occasional coworkers changes two settings in Task Manager that really irks the hell out of me, "Hide when minimized" and "Always on top". I want to make a little AutoIt script that intercepts these menu selections and moves the cursor away, kinda like the button-you-can't-press. Problem is, I can look for a window in an infinite loop, wait for it to become active (and start polling more frequently), but I can't figure out how to detect what item is under the cursor, or how to address an item on the screen. All I've worked with so far are hard-coded items So, any ideas on how I can accomplish this? Or even if it's possible? I'd love to stop seeing Task Manager down in the tray with those two options checked every few weeks