-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Behavior of the new RAT build. #71
Comments
Hey, |
@karma9874 😅 Sorry! Tested too early...! |
Everything is perfect after the new change ❤️ however, screen dim behavior is still there |
shell gotta closed when mobile screen is turned off ,,I am still facing this isse |
can I get that enhanced apk |
Hey, |
do fresh git clone and then follow the same step :) |
😍 You're the man :) Yes, screen dim is no longer seen and excluded the RAT from Android battery optimizations... It's ROCK SOLID 👍 Thanks for the hard work 👍 |
Hello @karma9874,
Thank you for adding the foreground service! :)
I have built a new APK with modified changes (foreground svc enhancement). Installed it in my Android 9 (Moto G6) mobile, and started to test the setup. After opening the RAT, got the reverse shell as expected, executed commands, all looks good (mobile unlocked at this point).
Manually disabled notifications, battery optimizations to ensure that the RAT functionality not be affected by those settings.
Now, I did notice the dim backlight behavior is still present i.e. screen did not get turned off completely instead it keeps the display on (dim) after crossing the config screen-off time (15 seconds in my case). So, I force locked the mobile and still the reverse shell is up and running, executed commands like takePic and startVideo, commands got executed successfully when the mobile is locked 😊 though it has some delay, it's absolutely fine to wait for some extra seconds...!
Sometimes, I do see RAT just stops working like there's no screen flicker when conn./disconn. to internet, no reverse shell, no display dim (mobile gets locked after 15 seconds). In that case, do we have any auto-restart logic or some kind of functionality to start the RAT service again?
To make it work again, I would need to reboot the mobile!!!
Thanks for your help!
The text was updated successfully, but these errors were encountered: