Tools.build:gradle:2.3.1 infected with HEUR: Trojan.AndroidOS.Boogr.gsh

Question

From today, when we create an application with the latest version of Android Studio and enable instant launch, Kaspersky starts to tell us that something is trying to introduce HEUR: Trojan.AndroidOS.Boogr.gsh in our .dex class. After some research, I found out that it starts when we use com.android.tools.build:gradle:2.3.1 instead of 2.3.0! I tested it on a brand new Mac book. Just download Android Studio by creating an empty project with Kaspersky installed with the latest updates and receiving a warning from Kaspersky. Can anyone check if this is true for him? Also with an old project that has been using 2.3.1 for several weeks, this does not happen, I think the reason for the cached version 2.3.1. Maybe someone changed something in 2.3.1 in the meantime.

Answer 1

I am really experiencing the same problem.

A workaround is to change the start of the run or downgrade gradleto 2.3.0.

For me, this only happens with an application in development. When you create a release version, everything works fine.

UPD (April 22). The problem is gone for me. It uses the same computer with the same settings with gradle 2.3.1 and enabled instant start - everything works fine.

Answer 2

We are studying it right now.

Answer 3

, Android Studio Windows 7 "Hello World", Instant Run USB Samsung Galaxy Core Prime. , Android Studio Android Studio, . , .

, , "Hello World", Kaspersky Trojan HEUR.Trojan.AndroidOS.Boogr.gsh. Kaspersky , . , Kaspersky . Android . Kaspersky , .

( Android) , , Kaspersky .

Answer 4

, , - , "Hello World" Android Studio, Kaspersky .

, , , , , Kaspersky. , , , Android Studio.

The next day (in Australia), I downloaded and installed a new copy of Android Studio with the first factory reset by my phone, used Kaspersky to clean up two suspicious virus components again, and then removed each component of Android Studio software from the computer. Subsequent checks of the system virus and the launch of Android Studio did not lead to a problem.

I do not know if Kaspersky and / or Android fixed the problem or whether it was isse with my system and fixed with my cleaning.