You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the detection issue
Sorry I'm not too familiar, but nothing looks obfuscated to me when I used jadx for decompilation. There is no difference in the result whether I include the debug option that apktool offers, so probably not an antidebug either; most likely a packer given the options?
APKiD current results...
$ apkid -v VirtualDesktop.Android.Quest2+.apk
[+] APKiD 2.1.5 :: from RedNaga :: rednaga.io
[*] VirtualDesktop.Android.Quest2+.apk!classes.dex
|-> anti_vm : Build.HARDWARE check, Build.MANUFACTURER check, Build.TAGS check, possible VM check
|-> compiler : unknown (please file detection issue!)
|-> yara_issue : yara issue - dex file recognized by apkid but not yara module
Additional context
I tried to decompile and recompile this apk using apktool (without making any changes to it), and when I launch it on my Quest 2 and monitor logcat, it seems like it's constantly being killed and restarted; in the headset, it just looks like infinite loading at the splash screen.
The text was updated successfully, but these errors were encountered:
Provide the file
https://github.com/guygodin/VirtualDesktop/releases/download/v1.32.9/VirtualDesktop.Android.Quest2+.apk
Describe the detection issue
Sorry I'm not too familiar, but nothing looks obfuscated to me when I used jadx for decompilation. There is no difference in the result whether I include the debug option that apktool offers, so probably not an antidebug either; most likely a packer given the options?
APKiD current results...
Additional context
I tried to decompile and recompile this apk using apktool (without making any changes to it), and when I launch it on my Quest 2 and monitor logcat, it seems like it's constantly being killed and restarted; in the headset, it just looks like infinite loading at the splash screen.
The text was updated successfully, but these errors were encountered: