/system/bin/log -p d -t su /dev/com.android.settings/.socket3458
/system/bin/log -p d -t su 10065 /system/bin/app_process64 executing 0 /system/bin/sh using binary /system/bin/sh : sh
/system/bin/log -p d -t su child exited
/system/bin/log -p d -t su client exited 1
/system/bin/log -p d -t su connecting client 3445
/system/bin/log -p d -t su connecting client 3564
/system/bin/log -p d -t su connecting client 3706
/system/bin/log -p d -t su connecting client 3826
/system/bin/log -p d -t su connecting client 3960
/system/bin/log -p d -t su connecting client 4109
/system/bin/log -p d -t su connecting client 4211
/system/bin/log -p d -t su connecting client 4386
/system/bin/log -p d -t su connecting client 4518
/system/bin/log -p d -t su connecting client 4616
/system/bin/log -p d -t su connecting client 4710
/system/bin/log -p d -t su connecting client 4780
/system/bin/log -p d -t su connecting client 4897
/system/bin/log -p d -t su connecting client 5041
/system/bin/log -p d -t su connecting client 5193
/system/bin/log -p d -t su connecting client 5310
/system/bin/log -p d -t su connecting client 5452
/system/bin/log -p d -t su db allowed
/system/bin/log -p d -t su remote args: 1
/system/bin/log -p d -t su remote pid: 3445
/system/bin/log -p d -t su remote pid: 3564
/system/bin/log -p d -t su remote pid: 3706
/system/bin/log -p d -t su remote pid: 3826
/system/bin/log -p d -t su remote pid: 3960
/system/bin/log -p d -t su remote pid: 4109
/system/bin/log -p d -t su remote pid: 4211
/system/bin/log -p d -t su remote pid: 4316
/system/bin/log -p d -t su remote pid: 4386
/system/bin/log -p d -t su remote pid: 4518
/system/bin/log -p d -t su remote pid: 4616
/system/bin/log -p d -t su remote pid: 4710
/system/bin/log -p d -t su remote pid: 4780
/system/bin/log -p d -t su remote pid: 4897
/system/bin/log -p d -t su remote pid: 4990
/system/bin/log -p d -t su remote pid: 5193
/system/bin/log -p d -t su remote pid: 5310
/system/bin/log -p d -t su remote pid: 5452
/system/bin/log -p d -t su remote pts_slave:
/system/bin/log -p d -t su remote req pid: 3424
/system/bin/log -p d -t su remote req pid: 3543
/system/bin/log -p d -t su remote req pid: 3675
/system/bin/log -p d -t su remote req pid: 3803
/system/bin/log -p d -t su remote req pid: 3937
/system/bin/log -p d -t su remote req pid: 4079
/system/bin/log -p d -t su remote req pid: 4190
/system/bin/log -p d -t su remote req pid: 4349
/system/bin/log -p d -t su remote req pid: 4489
/system/bin/log -p d -t su remote req pid: 4595
/system/bin/log -p d -t su remote req pid: 4730
/system/bin/log -p d -t su remote req pid: 4871
/system/bin/log -p d -t su remote req pid: 5019
/system/bin/log -p d -t su remote req pid: 5288
/system/bin/log -p d -t su remote req pid: 5420
/system/bin/log -p d -t su remote uid: 10065
/system/bin/log -p d -t su sending code
/system/bin/log -p d -t su starting daemon client 10065 10065
/system/bin/log -p d -t su su invoked.
/system/bin/log -p d -t su waiting for child exit
/system/bin/log -p d -t su waiting for user
/system/bin/log -p e -t su Getting exe path failed with 2: No such file or directory
/system/bin/log -p e -t su sqlite3 open /data/user_de/0/com.android.settings/databases/su.sqlite failure: 14
/system/bin/log -p w -t su request rejected (10065->0 /system/bin/sh)
sh
su
Uses elevated priveleges.
Gets information about network.
Gets information about phone status (number, IMEI, etc.).
Gets information about accounts associated with the device.
Displays its own windows over windows of other apps.
Curing recommendations
Android
If the mobile device is operating normally, download and install Dr.Web for Android Light. Run a full system scan and follow recommendations to neutralize the detected threats.
If the mobile device has been locked by Android.Locker ransomware (the message on the screen tells you that you have broken some law or demands a set ransom amount; or you will see some other announcement that prevents you from using the handheld normally), do the following:
Load your smartphone or tablet in the safe mode (depending on the operating system version and specifications of the particular mobile device involved, this procedure can be performed in various ways; seek clarification from the user guide that was shipped with the device, or contact its manufacturer);
Once you have activated safe mode, install the Dr.Web для Android Light onto the infected handheld and run a full scan of the system; follow the steps recommended for neutralizing the threats that have been detected;
Rinnovo versione di prova tramite AppGallery/Google Pay
Continuando a utilizzare questo sito, l'utente acconsente al nostro utilizzo di file Cookie e di altre tecnologie per la raccolta di informazioni statistiche sui visitatori. Per maggiori informazioni