A newly documented Android banking trojan called RemControl is using fake Google Play pages, phishing overlays and Android Accessibility permissions to target banking customers. The campaign was disclosed by Group-IB on September 23, 2026, and its findings matter beyond the named banks: the infection chain shows how a convincing app-install page can turn an ordinary sideload into full remote control of a phone.
This is not a claim that every Android device or banking app is affected. Group-IB says the campaigns it analyzed targeted more than 30 financial institutions across parts of Western Europe, the Middle East and Canada. The practical lesson is to recognize the installation and permission pattern before credentials are exposed.
What Group-IB found
Group-IB describes RemControl as a previously undocumented Android banking trojan operating through a Malware-as-a-Service infrastructure. The researchers observed samples dating to July 2026 and infrastructure active since May.
According to the report, malicious pages impersonate Google Play while offering a fake version of the third-party TVTap IPTV app. One observed campaign localized the page for Italian users and delivered the APK only when the visitor matched its device and location checks.
After installation, the payload requests Android Accessibility Service access. Group-IB says that permission is then abused to place phishing overlays over legitimate banking apps, capture keystrokes, stream the screen and remotely control the device. The researchers confirmed active overlays for more than 30 financial institutions in Italy, France, Spain, Poland, Portugal, GCC member states and Canada.
Why Accessibility permission is the critical warning
Accessibility is a legitimate Android capability intended to help users interact with their devices. The danger is not the feature itself but granting that level of control to an untrusted app. Google Play policy specifically prohibits using the Accessibility API to bypass platform security controls or manipulate the interface deceptively.
For an app downloaded from an unfamiliar website, an unexpected request for Accessibility access should therefore be treated as a major warning sign. Do not approve the permission simply because the installation page resembles Google Play.
The fake Play Store page is part of the attack
One of the most useful details in the RemControl research is the delivery path. The malware was not described as silently appearing on phones. Group-IB observed fake Google Play pages and malvertising that persuaded users to download an APK.
That distinction gives users an opportunity to break the chain. Check the browser address bar instead of trusting Play Store branding inside a webpage. If a website tells you to download an APK and then change security settings or enable powerful permissions, stop and verify the app through an official source.
What makes RemControl unusual
Group-IB says the dropper can use a local VPN service during installation in an attempt to interfere with Play Protect, and that installations can receive unique signing certificates. Its command-and-control address can also be obtained through an encrypted Telegram dead-drop, allowing infrastructure to change without rebuilding the malware.
The researchers also found artifacts indicating AI-assisted development in the operator infrastructure and phishing overlays, including an AI-assistant response left in a production phishing page. That finding should be interpreted narrowly: it is evidence about how parts of this criminal infrastructure were built, not evidence that an AI independently launched the campaign.
How Android users can reduce the risk
Google says Play Protect checks apps from Google Play and can also scan apps installed from other sources. It may warn about, disable or remove potentially harmful apps, and can block some unverified installations that request sensitive permissions commonly abused in financial fraud. Google recommends keeping Play Protect enabled.
- Prefer Google Play or another source you can independently verify instead of APK links from ads, messages or unfamiliar websites.
- Keep Play Protect enabled and pay attention to its installation warnings.
- Do not grant Accessibility access to an app unless you understand exactly why its core function needs it.
- Treat a banking login screen that appears unexpectedly, looks slightly different or overlays another app as suspicious.
- If you already installed a suspicious APK, avoid opening banking apps until the device has been checked and the suspicious app removed.
- If banking credentials, a PIN or card information may have been exposed, contact the bank through its official channel immediately.
What to do if you think you installed it
Disconnecting from the network can limit immediate communication while you assess the device. From a trusted device, contact your bank if financial credentials may have been entered. Review installed apps and Accessibility services for anything you do not recognize. Run Play Protect and follow any removal warning it provides.
If the phone continues behaving as though it is remotely controlled, or you cannot reliably remove the suspicious software, preserve important personal data carefully and seek device-manufacturer or qualified security support before restoring sensitive accounts. Change important passwords from a separate trusted device rather than from the potentially compromised phone.
For related checks, use SSM Apps’ Google Play Protect warning guide and Android app permissions guide.
Sources
Primary research: Group-IB — RemControl: AI Built the Overlays. Victims Lose their PINs, September 23, 2026.
Android protection guidance: Google Play Protect Help. Accessibility policy context: Google Play Developer Programme Policy.
Bottom line
RemControl is a newly documented campaign, not a reason to panic about normal Android banking. Its infection chain depends on familiar social-engineering steps: a fake store page, an APK installation and unusually powerful permissions. Verifying the source of an app and refusing unexpected Accessibility requests can interrupt that chain before a banking overlay ever appears.

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