NPCI has reached out to Google over malicious UPI APKs that fraudsters push through WhatsApp and fake support links, not the Play Store. This article covers how sideloading those fake payment apps works, what the November 2026 MediaNama report actually says (and does not claim), why UPI apps raised the alarm, and the simple rules Tamil Nadu users should follow: install GPay, PhonePe, Paytm, BHIM and bank apps only from Google Play, never from a chat file.
- Media reports say NPCI reached out to Google after UPI apps flagged sideloaded Android APKs as a major fraud route.
- Fake payment Apps travel through messaging chats and fake customer-support links, not Play Store.
- Sideloading means installing an APK from outside Google Play. That tap is the open door.
- The report does not announce a Google fix, a ban, or a date. Your Phone settings have not magically changed.
- Install GPay, PhonePe, Paytm, BHIM and bank Apps from Play Store only. Never from WhatsApp, Telegram or SMS.
What just happened?
It is 9 pm. A WhatsApp ping lands. "Your UPI will be blocked in 24 hours. Install this update." There is a file. It looks like GPay. Install is one tap away.
That file is the whole story.
According to a November 2026 MediaNama report, NPCI has reached out to Google. The trigger was UPI apps raising an alarm. Fraudsters are distributing malicious Android application packages - APKs - through messaging apps and fake customer-support links. People then sideload those Apps from anywhere except the Play Store.
Sideloading, in one line: you install an App from a random file, not from Google Play.
NPCI is not a random startup. It operates UPI, the rail that moves money from your bank account to a tea stall in three seconds. When UPI apps say fake APKs are eating users, Google is the obvious address. Android is Google's house. Play Store is Google's shop. Unknown-source installs are the side gate.
The report, as publicly described, does not print a Google reply. It does not name a new Android switch. It does not give a deadline. So this is not "Google banned APKs in India" news. This is "India's payment operator walked up to the Phone OS maker and pointed at the side gate" news.
Keep that distinction. Headlines will try to melt them together.
UPI apps have spent years saying the same thing in banners: we will never ask you to install a file from WhatsApp. NPCI going to Google suggests those apps decided posters are not enough. The distribution channel - chats, fake support pages, APK files - sits on Android's permission to install from unknown sources.
If you remember one thing: the kit is not a cinematic hack of UPI's servers. It is a fake App on your Phone, put there by your own Install tap.
How does this actually work?
Start with the file.
An APK is just an Android installer. Play Store uses APKs too. The difference is who signed it, who scanned it, and who can yank it when it turns nasty. A Play Store listing goes through Google's checks. Play Protect can warn you. A Telegram document has none of that pipeline. It is a blob named something like GPay_Update.apk.
Android, by design, lets you install from outside Play. You enable "Install unknown apps" for Chrome or Files or WhatsApp. After that, the Phone treats that APK almost like a store App - icon, permissions popup, the lot.
Fake customer support is the social layer on top.
A UPI payment fails. Or a collect request you did not expect pops up. You search "GPay customer care" or you tap a number in an SMS. The voice on the line is calm. They say KYC is pending, or your UPI ID is frozen, or a refund needs a "secure App". They send a link. The page looks busy and official. You download. You tap Install. You tap Allow on accessibility because they said the App will not work otherwise.
Accessibility is the dangerous permission here. In honest Apps it helps people who cannot see the screen. In a malicious APK it can read what you type, including a UPI PIN, and it can tap buttons for you.
Overlay permission lets a fake screen sit on top of real GPay. SMS permission lets it swallow OTPs. Device admin makes uninstall a fight. None of this needs you to be "bad at technology". It needs you to be in a hurry, a little scared about a blocked account, and used to installing files.
That last part is very India. We sideload WhatsApp updates, video Apps, old games, modified APKs. The hand already knows the path. Fraud kits just put a UPI mask on the same path.
Messaging apps make it worse because they feel private. A file from a chat does not look like a random website. It looks like a person helping you. Family groups forward "official" APKs with zero malice and full damage. Some files even clone the icon and name of PhonePe or a bank App. You think you opened the real thing. You opened a lookalike.
Google is not clueless. Play Protect exists. Newer Android versions nag harder about unknown sources. Restricted settings block some powerful permissions for Apps that did not come from Play. All of that helps. All of that still leaves a door, because Android still wants to be an OS you can install software on without Google's shop.
That door is exactly what NPCI is asking Google to think about, if the MediaNama report's framing holds.
What changes for people in India?
Today, 21 November 2026, your Phone settings have not magically changed because of this report.
UPI still works. Pay the electricity bill. Split the biryani. Do it from the official App.
What may change is the temperature around Android policy in India. NPCI plus UPI apps is not a small lobby. If Google moves, the move will likely show up as tougher warnings, tighter unknown-source rules, or extra scrutiny when an APK asks for payment-sensitive permissions.
We do not have a product announcement to describe. Anyone telling you "Google will ban sideloading next week" is filling gaps. We will not.
There is a real trade-off if the side gate gets heavier. Plenty of Indians still sideload for reasons that have nothing to do with stealing PINs. An App that left Play Store. A version that works on an old Phone. A regional App that never listed. Developers without a Play billing setup. If unknown sources become painful, those people feel it.
That is a fair product argument. It does not make a fake UPI APK from a "support" chat any safer.
For UPI apps themselves, the practical change is already overdue: scream louder inside the App that they will never send an APK. Train customer-care journeys so a real agent never asks you to install a file. Some apps already do this. The ones with leaky "support" flows are part of the mess even when they did not write the malware.
Banks will keep repeating the same SMS. Delete it if it has a download link.
UPI already has safety rails - payee cool-downs, PIN on the App, dispute buttons. Those help after an account is in your name. They do not help if a fake App is sitting on the screen watching you type. That is why this conversation moved from "please educate users" to "please, Google, look at sideloading".
One more India-specific bit. Feature-phone UPI exists, but the pattern in this report is about Android APKs. If your parents use a smartphone to pay the milkman, this is their story. The kirana QR does not care. The Phone does.
What should you do now?
Treat every APK in a chat as a stranger with a key to your bank.
Install GPay, PhonePe, Paytm, BHIM, Amazon Pay and your bank App from Play Store only. Type the name yourself. Look at the developer line. Update from the Store's Update button, not from a website named gpay-support-secure with three hyphens.
If a message says your UPI is blocked, open the official App yourself. If the App works, you are not blocked. If it does not, use in-app help or the number on the back of your debit card - not the number in the SMS.
Turn off install-unknown-apps for WhatsApp, Telegram, Chrome, Gmail and Files. Path is roughly Settings, then Apps, then special app access, then install unknown apps. Leave it off. If you genuinely need to sideload something unrelated, enable it for one source, install, disable it again.
Never grant accessibility, device admin or screen overlay to an App you just downloaded from a link. A real UPI App from Play Store does not need a stranger on a call to "enable extra permission so we can unblock you".
If you already tapped Install on a suspect file: uninstall it. Check accessibility settings and device-admin Apps and remove anything you do not recognise. Then, from the official UPI App, change your UPI PIN. If money left, call the bank and use the dispute flow in the official App. Do not "fix" it by installing another file the same caller sends.
Talk to the people at home who already pay on UPI. The MediaNama report is about NPCI and Google. The actual Install tap is in your hall. A five-minute demo of Play Store beats a forwarded panic message.
Keep Play Protect on. It is a seatbelt, not a cage. New malicious APKs often look clean for a day or two. Your refusal to install from a chat is still the main control.
None of this requires you to wait for Google's reply to NPCI. The reply may take months. The next fake APK will not.




Comments (0)
Be the first to comment!