SOTI Pulse Logo

Wi-fi Malware issue Android 11

VT
Valentin Todorov

Hello colleagues.

I have the following case. I have a Samsung S20 and I have an activated "Antivirus" profile. After last update on android, SOTI catches com.android.wifi.resources that it is Malawere and tries to delete it, therefore android does not allow to delete the main process of system. A continuous cycle is obtained, from which there is no way out. I want the problem to be solved without introducing a factory reset device. If I try to remove the policies - they will stand with the status Waiting and nothing happens.

4 years ago
Android
ANSWERS
J
JSMOD@SOTI
4 years ago

Hi Valentin,

Thank you for posting on SOTI Central.

You should be able to configure the Antivirus policy to whitelist the process like below, just paste the full bundle ID into the 'Name' box:

Antivirus Whitelist

Kind regards,

JH
Jorge Hussni - SAFIRA Telecom
4 years ago

Hello @Valentim,

What is the model and brand of the device?

JSMOD,

This will happen in all Android 11? We have a big variety of device in Brazil operations and this kind of information is very usefull to turn on our attention for some brand or device model.

J
JSMOD@SOTI
4 years ago

Hi Jorge,

Are you referring to "com.android.wifi.resources" being caught by the Antivirus? If so, this simply depends on Bitdefender which powers MobiControl Antivirus profile. If you want, you can open a new case with SOTI Support (support@soti.net) and we can request that this bundle ID is permanently whitelisted in the future to save from configuring a Whitelist every time.

@Valentin if this suggestion worked for you, kindly mark the appropriate comment as 'Solution' to help other users find the answer.

Kind regards,

RC
Raymond Chan Diamond Contributor
4 years ago

Android 11 has only been rolled out for a very very small number of devices of each major device brand.  At the moment, isn't it too early now to say that the app module  com.android.wifi.resources  will always be incorrectly marked as malware and be requested to be added to the whitelist PERMANENTLY?  Shouldn't there be similar problem in more device models reported before such request be considered?

Similar Discussions