The bank app that arrives as a file
The I4C's banking-trojan warning: treat an unsolicited app file claiming to be from your bank as a suspected trojan until the bank itself says otherwise - the permissions that give it away, and the exact order to limit the damage.
The message says your bank account will be blocked, your KYC has expired, or your reward points lapse tonight - and it helpfully includes the fix: a link, or an app file attached right there. India's cyber-crime coordination centre, the I4C, has had a name for what sits at the other end of that file since its advisories listing of 21 April 2022: banking trojans, malware built to steal the confidential information on your phone. An app file you never asked for is not a shortcut to your bank's app. Until the bank itself says otherwise, treat it as a suspected trojan.
How the play runs
The fake app is built to be believed: it copies the bank's name, colours and login screen, and it arrives as an Android APK file over WhatsApp or SMS, behind a message engineered for urgency, as Outlook Money reported in October 2026 when covering the RBI's warning about fake banking apps. The I4C's National Cybercrime Threat Analytics Unit described a second route in an advisory of 26 August 2026, reported by the Hindustan Times: advertisements on social media that lead to lookalike sites, which then persuade the visitor to download an APK from outside the Google Play Store. That advisory named apps operating as "Night Play", "Reloop", "Kyss", "Vimo", "Rivo", "Nexo" and "Vixa", and similar variants. iPhone owners get the parallel version: a separate I4C listing entry of 15 January 2026 describes investment scams pushing sideloaded iOS apps that abuse configuration and provisioning profiles.
What the app does once it is in
The install is only the doorway. On first run the app asks for permissions: access to your text messages, contacts, call logs and notifications, and the two that matter most - Accessibility access and permission to display over other apps. With those, the NCTAU advisory explains, the malware can read what is on your screen, click buttons, enter OTPs or PINs, confirm transactions and initiate fund transfers. A fake login screen placed over your real banking app harvests what you type. Outlook Money's report adds that such apps forward intercepted OTPs to the fraudsters. Some go further: the August advisory describes a second app installed later, disguised as an update to the first, and in some cases a VPN that routes the phone's traffic through the attackers' servers. And the app may try to stop you removing it through normal settings.
The two tells that need no technical eye
First, the route. Official app stores review what they list; installing from a file bypasses those checks entirely, which is why the NCTAU's standing advice is to install apps only from the Google Play Store or other trusted app stores, and never from files pushed through ads, unknown links or messages. Even inside the store, verify before you trust: a store listing by itself is not proof of who published an app, so reach the listing from the bank's own website - an address you type, not a link that arrived - and check that the named developer is the bank. Outlook Money's report notes that Indian banks are moving their websites to the .bank.in domain, so a link claiming to be your bank on an unrelated address deserves scrutiny. Second, the asks. Treat Accessibility access as the crown jewels: it lets an app read and drive your other apps, and the NCTAU advises against granting it to unfamiliar applications. Keep "Install unknown apps" switched off, Google Play Protect on, and the phone's operating system updated.
If you already installed it
Contain first, clean up second - the order matters more than the tools. Cut the app's connection: turn off mobile data and Wi-Fi on the suspect phone. Flight mode alone is not enough, since Wi-Fi can stay or be switched back on; turn Wi-Fi off explicitly. Then, from a different, trusted device, make the calls that limit the damage before you touch the suspect phone again: your bank, on the number printed on your card or passbook, to block cards, suspend net banking and UPI, and change your passwords and UPI PIN - and, if money has already moved, call 1930 immediately, the national financial-fraud helpline, and file at cybercrime.gov.in. Containment comes before cleanup: those calls first, the removal after. Then remove the app. Uninstall it; if it refuses, revoke its Accessibility and device-administrator permissions first. The August NCTAU advisory and Google's own malware-removal guide both describe restarting in Safe Mode and uninstalling from there when normal removal fails - a technique that works in many cases, not a guarantee. If the app persists or reappears, back up what matters and consider a factory reset as a last resort - no removal step, reset included, is a guarantee on its own - and get qualified technical help if you are unsure. Either way, treat every password that ever touched the phone as exposed, and change those from the trusted device regardless. Keep the complaint number, screenshots and the original message - they are the evidence every later step asks for. The message or call that carried the file can be reported through the Chakshu facility on the government's Sanchar Saathi portal.
What reporting early is worth
The rules in force today give speed a legal value. Under the RBI's customer-protection circular on limiting liability in unauthorised electronic banking transactions, your liability is zero where the deficiency lies neither with you nor with the bank - a third-party breach - provided you notify the bank within three working days of receiving its transaction communication; notified within four to seven working days, your liability is limited to the transaction value or the ceiling in the circular's table, whichever is lower; beyond that, the bank's board-approved policy decides. The RBI's amendment directions of 24 June 2026 rewrite the framework for transactions from 1 January 2027: the zero-liability window for third-party breaches becomes five calendar days from the transaction, "downloading malicious apps" is named explicitly among the examples of customer negligence, and a new mechanism compensates small-value fraud - gross losses up to 50,000 rupees - at 85 per cent of the net loss or 25,000 rupees, whichever is less, once in a lifetime, where the victim reports to the bank and to 1930 or the cyber-crime portal within five calendar days. The burden of proving customer liability sits with the bank, not with you. None of this is a promise about any one case - but every window in the framework rewards the same thing: report early.
The shape worth remembering
A bank reaches you through the app you went and got yourself, from the listing its own website points to. A fraudster reaches you through the file they sent. An app file that arrives uninvited is not a service channel. Treat it as a suspect, and let the bank itself clear it or condemn it.
Sources: the I4C advisories page - official listing of the advisories "Banking Trojans (Malware) stealing confidential information to defraud citizens" (21 April 2022) and "Malicious Sideloaded iOS Apps abusing configuration/provisioning profiles" (15 January 2026); RBI's customer-protection circular on limiting liability in unauthorised electronic banking transactions - the zero-liability and limited-liability rules in force today, including the three-working-day window for third-party breaches and the burden of proof on the bank; RBI's amendment directions of 24 June 2026 - effective for transactions from 1 January 2027: the five-calendar-day window, "downloading malicious apps" as named customer negligence, and the small-value compensation mechanism; Outlook Money, 24 October 2026 - the RBI warning on fake banking apps: APK distribution over WhatsApp and SMS, copied branding, permission abuse and OTP forwarding; the Hindustan Times, 31 August 2026 - the I4C NCTAU advisory of 26 August 2026: ad-led APK distribution, the named apps, Accessibility abuse, and safe-mode removal advice; Google's malware-removal guide - Play Protect, updates and removal steps for unsafe apps; the government's Sanchar Saathi Chakshu portal - the reporting route for suspected fraud communications, verified live. Fraud reporting: 1930 and cybercrime.gov.in.
Frequently asked questions
The message had my bank's logo and name. Still fake?
The branding proves nothing: the logo, colours, name and login screen are all public and copying them is free. Judge the delivery, not the decoration. An app file or link that arrives unsolicited is a red flag, not a verdict - treat it as suspected malware and check with the bank through its official route before installing anything. The genuine app is the listing your bank's own website points to, with the bank named as developer, reached by you rather than by a message.
Can an iPhone get this?
The same play exists for iPhones in a different costume. The I4C's listing of 15 January 2026 describes investment scams that push sideloaded iOS apps abusing configuration and provisioning profiles - the iOS mechanism for installing apps outside the App Store. The rule transfers whole: an app or profile that arrives through a message or an ad is not an investment platform, it is the way in.
I granted the permissions but no money is gone. What now?
Do not wait for a loss to confirm the diagnosis. Turn off mobile data and Wi-Fi, then from a different device change your banking passwords and UPI PIN and ask the bank to review your cards and access. Then uninstall the app - revoking Accessibility and device-administrator permissions first if it resists - and watch your statements over the following weeks. Acting before money moves is the good outcome, not an overreaction.
Will I get the money back?
No one can promise that, and anyone who does is running the next scam. What speed buys you is the best available position: under the RBI circular in force today, third-party-breach cases carry zero liability when you notify the bank within three working days of its transaction communication, and the amendment directions effective for transactions from 1 January 2027 extend that window to five calendar days while naming malicious-app downloads as customer negligence. The burden of proving your liability sits with the bank - report early, to the bank and to 1930.