Incident sheet · /security
- System
- Security & Risk
- Filed
- Read
- 3 min · 677 words
- Severity
- Routine
NPCI and UPI Apps Ask Google for Android-Level Fraud Blocks
NPCI and UPI payment apps have asked Google to restrict sideloaded APKs from gaining overlay, accessibility and device-admin permissions, as overlay trojans intercept UPI PINs.

Event log
- NPCI and UPI payment apps have approached Google for Android-level safeguards against malicious sideloaded apps.
- Ghost Overlays and GhostBat RAT variants abuse Android's 'display over other apps' permission to steal UPI PINs.
- Google's stricter sideloading flow took effect in August 2026.
- Free limited distribution accounts will allow sharing apps with up to 20 devices without fees or ID.
India's National Payments Corporation of India (NPCI) and UPI payment applications have approached Google directly, asking for Android-level safeguards against malicious apps that compromise devices and enable payment fraud, The Economic Times reported. The move signals that the industry now sees the operating system, not the careless user, as the front line of the problem.
What changed in the industry's approach?
Until now, fraud prevention concentrated on user behavior: sharing one-time passwords, scanning fraudulent QR codes, or approving deceptive collect requests. Payment applications say that approach no longer covers the threat, because attackers exploit legitimate Android features and sideloaded software rather than user naivety.
Fraudsters distribute malicious Android application packages (APKs) through messaging apps, fake customer support links and spoofed update prompts. Because these apps are sideloaded — installed from outside the Google Play Store — conventional in-app security measures cannot always detect or block them, leaving payment providers exposed to financial liabilities from frauds beyond their control.
A payment application official put the demand plainly: "The system should restrict critical permissions for sideloaded APKs, enforce strict OS-level blocks preventing apps installed outside vetted app stores from requesting accessibility services, device admin, or overlay permissions without multi-step safeguards." Awareness campaigns, the official said, are not enough.
How does the attack actually work?
The core problem is a single Android permission. Overlay malware — including variants dubbed Ghost Overlays and the GhostBat Remote Access Trojan — abuses Android's 'display over other apps' permission to place invisible layers on top of legitimate applications. When a user types a UPI PIN into what looks like their payment app, the overlay captures the entry and transmits it to the attackers.
Several banks have warned customers against downloading APKs from unknown numbers and links. Those warnings, however, do not remove the underlying exposure. In short: the malware does not break the payment app, it sits above it and reads what the user types.
Who said what?
Vishwas Patel, chairman of the Payments Council of India (PCI), confirmed the engagement with Google. "This is an App world issue. Feedback has gone to Google from many in the app ecosystem and we believe that Google is doing whatever it can to minimise frauds from malicious, sideloading third-party applications on the Android operating system," Patel told The Economic Times.
What can banks and fintechs do on their side?
The report outlines two complementary defenses:
- Device integrity checks before transactions. Devices with outdated security updates or suspicious behavioral signals could face transaction limits or extra verification, rather than automatic exclusion from payment services.
- Server-level attestation. Android devices carry a private attestation key in their security hardware to prove authenticity. Since Google revokes leaked keys, service providers should check device attestations against Google's list of cancelled keys and reject devices that fall below minimum security patch levels.
An industry source suggested Google could enhance its Play Integrity API — already integrated into payment applications — to detect and blacklist devices using leaked keys. The industry is also reviewing whether Google's recent security patches are sufficient and whether Indian Android devices have actually received them. Google has introduced 'restricted settings' in newer Android versions to limit permissions for sideloaded apps, but many users in India still run older devices that lack these protections.
What has Google already shipped?
In August 2026, Google's tougher sideloading flow for apps from unverified developers took effect. Users must enable developer mode, confirm they are not being coached, restart the device, and wait one day before authenticating with biometrics or a PIN. They can then install such apps for seven days or indefinitely, with additional warnings.
Google will also offer free limited distribution accounts to students and hobbyists, letting them share apps with up to 20 devices without fees or government identification. The measure accompanies a developer verification policy requiring identity checks for anyone distributing apps outside the Play Store.
The gap the industry now wants closed is simple: apps installed outside vetted stores should never get the permissions that let them read a payment PIN.
via medianama.com (Source)
More from Amara Osei
Show full bio
Correspondent covering regulation, policy and their impact on enterprise information technology and the leaders who run at CIO Monitor.
187 articles
The newsroom digest
One email a day with the stories that matter. No noise.
Cross-references
- PayU hit by alleged ₹25.67 crore cloud breach; two arrested
- Kaspersky blocks 1,668,368 mobile attacks in Q3 2026
- AI-assisted hackers diverted Rs 65 crore in approved loans from 12 NBFCs
- SIM Binding Will Cut Cybercrime by 2-3% at Most, Experts Warn
- Hardcoded Password in Wyndham App Exposed Millions of Customer Records