NPCI Wants Overlay Permissions Restricted on Sideloaded Apps; Google's 2024 India Block List Omits Them
Security / news
NPCI Wants Overlay Permissions Restricted on Sideloaded Apps; Google's 2024 India Block List Omits Them
The reported ask covers accessibility, device admin and display-over-apps. The pilot Google announced on Oct. 3, 2024 named four other permissions.
India's payments industry wants Google to restrict three Android permissions for sideloaded apps, according to a report from The Economic Times that MediaNama summarised on Nov. 19. Google's own India protection, announced in October 2024, covers a different list of four permissions, and "display over other apps", the one the reported overlay malware abuses, was not on it.
Whether Google has widened the list since does not appear in any of the pages consulted for this report. Neither Google nor NPCI is quoted in the coverage.
What was reported on Nov. 17 and 19
Business Today, dated Nov. 17, and MediaNama, dated Nov. 19, both say the National Payments Corporation of India (NPCI) has started talks with Google about operating-system-level safeguards. Both attribute the account to The Economic Times, and neither names the people behind it. The original ET article was not among the pages fetched.
The attack both describe is a malicious APK spread through messaging apps, fake customer-support links or spoofed update prompts. Overlay malware, named as Ghost Overlays and variants of the GhostBat remote access trojan, abuses "display over other apps" to capture a UPI PIN.
MediaNama quotes Vishwas Patel, chairman of the Payments Council of India, saying feedback had gone to Google and that Google is "doing whatever it can" to curb sideloaded app fraud.
What the industry is asking for
The proposals listed by MediaNama are specific.
- Block non-vetted apps from requesting accessibility, device administration or overlay permissions without multi-step safeguards.
- Let banks and fintechs add transaction limits for devices with outdated security patches or suspicious behaviour.
- Check device attestation keys against Google's list of revoked keys, and have Google extend the Play Integrity API to flag devices using leaked keys.
What Google already does in India
Google announced the pilot at its Google for India event on Oct. 3, 2024, according to TechCrunch. Play Protect blocks a sideload that arrives through a browser, a messaging app or a file manager when the app declares certain permissions. Offline apps and third-party app stores remain usable.
Google said its analysis of major fraud malware families found more than 95% of suspicious installs came through those channels. In Singapore, where it launched in February 2024, TechCrunch reports it prevented 900,000 high-risk installs in six months.
| Permission | In Google's 2024 India list | In the industry's reported ask |
|---|---|---|
| Accessibility | Yes | Yes |
| RECEIVE_SMS and READ_SMS | Yes | Not named |
| BIND_Notifications | Yes | Not named |
| Display over other apps | Not named | Yes |
| Device administration | Not named | Yes |
The overlay permission is the gap in Google's 2024 list
The overlap on accessibility is real. The gap is the overlay permission. A pilot built around SMS interception and screen reading, which Google said fraudsters abuse to intercept one-time passwords and spy on screen content, does not obviously stop an overlay that sits on top of a UPI app and reads a PIN as it is typed.
MediaNama also reports changes effective August 2026 for apps from unverified developers: developer mode, a restart, a one-day wait and biometric or PIN confirmation before install. It also notes that restricted settings in newer Android versions limit permissions for sideloaded apps, while many Indian users still run older devices. The coverage does not say how many.
What it means for banks and users
Nothing here is a patch. It is a request, and the coverage does not give a date. Banks have told customers not to install APKs sent from unknown numbers or links, and that remains the only control the reporting describes that works today on an older phone.
For related Indian incidents where the defence assumed too much, see the Delhi-NCR lender case and the e-sushrut CERT-In advisory. The next observable step is a statement from NPCI or Google on whether the permission list is changing.
Sources
More in Security
- 01Ruby2Shell (CVE-2026-132825): Ruby Is Fixed, but GitLab, GitHub Enterprise and Chatwoot Are Listed Without a PatchA one-byte heap overflow in Ruby's case conversion carries a 7.4 local score, while the researchers say stock Rails is remotely reachable and will publish a proof of concept Nov. 25.
- 02CVE-2026-99312: A KVM Nested-AMD Bug Scores 8.8, With Fixes Listed for Three Kernel BranchesThe Linux CNA's scoring notes describe a freed page-table root that a guest can aim at; the commit message describes only a stale MMU context.
- 03CISA's Nov. 18 KEV Additions Include Apache Axis 1.x, Which Has No Fix, With a Nov. 21 DeadlineThree of four new entries carry a three-day federal deadline; LiteLLM's advisory names two different patched versions.
- 04NSANet Went Down Nov. 17 With 'Routine Maintenance' as the Only Cause on RecordOfficials from the White House to the Senate Intelligence Committee say they see no attack, but the NSA has not said which systems failed or for how long.