Android banking malware often depends on permissions and settings that users can inspect themselves. A single unusual setting does not prove that a phone is infected, but combinations such as an unfamiliar sideloaded app, Accessibility access, overlay permission, unexpected Wireless Debugging or a cloned banking app deserve immediate attention.
Recent threats such as RatHat and Gigabud show why these checks matter. RatHat has been documented abusing Accessibility and local ADB pairing, while Gigabud has used a malicious work-profile setup to isolate cloned banking apps. The goal of this guide is not to diagnose malware from one symptom; it is to help you identify warning signs worth investigating.
1. Review recently installed apps
Open Settings → Apps and sort or review recently installed applications. Pay extra attention to apps installed from links in SMS messages, ads, social media, unofficial stores or direct APK downloads.
If you do not recognize an app, do not immediately launch it to “see what it is.” Check its package details, installation source and permissions first. Our Android app safety checklist covers that process in more detail.
2. Check Accessibility access
Accessibility services can legitimately help users control a phone, but they can also read interface content and interact with apps. Google warns that restricted settings can expose sensitive information and should only be enabled for developers you trust.
Search Android Settings for Accessibility and review installed or downloaded services. A normal streaming, shopping, delivery or “system optimizer” app should not need broad Accessibility control without a clear reason.
3. Check “Display over other apps” permission
Banking trojans can use overlays to place a fake login form over a legitimate banking app. Search Settings for Display over other apps, Appear on top or Special app access. Review unfamiliar apps with that permission.
4. Check Developer Options and Wireless Debugging
Wireless Debugging is a legitimate Android developer feature. Google documents it under Developer options for pairing Android devices with development tools over Wi-Fi.
If you never enabled Developer Options or Wireless Debugging but find them active, investigate why. RatHat researchers documented malware using Accessibility to enable Developer Options, turn on Wireless Debugging and pair with the local ADB daemon.
5. Review paired wireless-debugging devices
If Wireless Debugging is enabled, open its settings and review paired devices. Remove pairings you do not recognize. Developers who actively use ADB should distinguish their own workstation from an unexplained pairing rather than simply disabling everything.
6. Look for an unexpected work profile or cloned banking app
A work profile can be completely legitimate. Employers and privacy tools use them. But if you never created one and suddenly see a second copy of a banking app, a work-badge icon or an unfamiliar profile-management app, investigate it.
Security researchers have documented Gigabud using a malicious work-profile environment to run a cloned banking app separately from the personal profile.
7. Run Google Play Protect
Open Google Play → your profile → Play Protect and run a scan. Google says Play Protect checks apps from Google Play and other sources for potentially harmful behavior and can warn, disable or remove harmful apps.
Keep Scan apps with Play Protect enabled. If you install apps outside Google Play, Google’s “Improve harmful app detection” option can provide additional analysis of unknown apps.
8. Check device and Google Play system updates
Install current Android security and Google Play system updates. Patching will not remove every active infection, but it closes known vulnerabilities and updates platform defenses.
9. Watch for banking symptoms that need immediate action
- Login prompts that look different from the bank’s normal interface.
- OTP or SMS messages disappearing unexpectedly.
- Accessibility or overlay permissions becoming enabled for unfamiliar apps.
- A banking app appearing twice or inside an unknown work profile.
- Developer Options or Wireless Debugging enabled without your action.
- Uninstall attempts that fail with suspicious or fake-looking dialogs.
10. If banking malware is confirmed, protect the account first
Use a separate trusted device to contact your bank and change important credentials. Do not rely on the suspected phone for password changes if you believe screen capture, overlays or input monitoring may be active.
For a confirmed RatHat infection, current security guidance recommends a factory reset because its documented persistence can survive normal app removal. Back up irreplaceable personal files carefully and avoid restoring unknown APKs afterward.
For the technical RatHat attack chain, see our RatHat Android malware explainer. If your concern started with a downloaded APK, also read our Android sideloading safety guide.
Sources
- Malwarebytes — RatHat Android banking malware analysis
- Malwarebytes — Gigabud work-profile banking attack
- Google Play Help — Play Protect
- Android Developers — Developer options and Wireless Debugging
Featured image: “Smartphone lock screen enter PIN” by Mykhal, CC0, via Wikimedia Commons.

Start the conversation
Corrections, useful experiences and focused questions are welcome. Keep discussion respectful and on topic.