This afternoon my phone wouldn’t let me open any apps, Avast had detected a trojan in all of my apps. The trojan was: Android:GinMaster-CO[trj]. Is this a false positive or can i somehow remove this trojan?
without direct access to the device it’s hard to tell wether it’s a false positive or not.
I’d un- and reinstall Mobile Security to make sure the detections aren’t a result of corrupted virus definitions.
unfortunatelly wrong virus definitions have been released for a brief amount of time. We are working on a fix and once it is released, I’ll let you know (so you can manually check for updates and don’t have to wait for the automatic process to kick in).
I have the same issue, today I woke up to see avast detected as trojan most of my apps, including the launcher [Trebuchet[, Gmail, Facebook, Twitter, and so on…will try the reinstalling Mobile Sec., hope it fixes the problem.
this was very annoying. 9 Apps recognized as false positives! I couldn’t use my Nexus 4 (Android 4.4.2) quite a while because avast repeatedly crashes.
After updating to 140109-01 and full rescan all is OK again.
What are the plans of avast optimizing the update processes so that this kind of failure will be avoided?
VINCENT STECKLERDecember 4th, 2009
Apologies for Bad Definition Update
You may have heard that we released a virus database update early Thursday morning (or Wednesday night depending on the time zone). We are deeply sorry for releasing this update and the trouble it caused you. Of the users that received the update, most encountered no problems, some encountered minor issues, and some had significant problems.
I apologize to each and every one of you—I realize that security is fundamentally about trust and you have to trust your security provider. We made a mistake here and it won’t happen again.
We have highly automated systems and processes for testing and releasing virus updates. Updates are thoroughly tested before being released. But the process failed due to a “human failure”. This was an example of the old proverb “the road to hell is paved with good intentions”. Some engineers thought they were doing the right thing by sending out an out-of-cycle update to fix a problem. Unfortunately, they circumvented the automated systems and ended up sending out the wrong update—one that had not yet been tested.