Google Enforces Verified Developer Registration for Android App Distribution
Google has set September 30, 2026 as the first enforcement date for new Android developer verification rules that tie app distribution to verified publisher identities. The initial rollout will apply to certified Android devices in Brazil, Indonesia, Singapore, and Thailand, where developers distributing apps through participating stores must complete identity checks through the Android Developer Console by submitting personal or organizational details such as legal identity, contact information, and in some cases a DUNS number. Google said the move is intended to make anonymous publication of malicious apps harder and improve accountability across the Android app ecosystem.
The controls will extend beyond Google Play to participating marketplaces including HONOR App Market, OPPO App Market, Samsung Galaxy Store, Palm Store, vivo V-Appstore, and Xiaomi GetApps, with broader expansion planned in 2027. Google is also adding APIs and a system service for app registration, verification checks, and bulk management through CI/CD workflows, alongside operational safeguards for APK testing and account management. After enforcement begins, only apps registered by verified developers will be allowed to install or update on certified Android devices in affected markets, though sideloading will remain possible through Android Debug Bridge or a new advanced installation flow for unverified developers.
Get ahead of threats like this
Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
How this story unfolded
4 events from the most recent confirmed update back to the earliest known activity.
Google sets Sept. 30, 2026 enforcement date for initial Android markets
Google announced that Android developer verification protections will take effect on 2026-09-30 for users in Brazil, Indonesia, Singapore, and Thailand. After that deadline, only apps registered by verified developers can be installed and updated on certified Android devices in participating markets, though sideloading remains possible through ADB or a new advanced installation flow.
Google plans broader Android verification expansion in 2027
Google said the developer verification and app registration requirements will expand beyond the initial markets to certified Android devices globally in 2027. The broader rollout also extends across additional participating app marketplaces in the Android ecosystem.
Google announces stronger Android developer verification requirements
Google introduced stricter identity verification requirements for Android developers and organizations publishing apps, requiring verified personal or organizational details in the Android Developer Console. The changes also include operational safeguards around APK distribution, testing, account management, and API-based CI/CD workflows.
Google announces mandatory Android developer verification requirement
Google said in August 2025 that Android developers publishing apps on certified Android devices would be required to verify their identity and register app package names. The policy was described as applying first in Brazil, Singapore, Indonesia, and Thailand, with broader rollout planned later.
Related entities
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Sources
5 references tracked. Mallory keeps watching after this page renders.
Google Sets Sept. 30 Deadline for Android Developer Verification in Four Countries
thehackernews.com
Open sourceGoogle sets timeline for Android developer verification enforcement - Help Net Security
helpnetsecurity.com
Open sourceGoogle ����������� ������ ��������� ����������� ������������� Android-����������
opennet.me
Open sourceGoogle ����������� ������ ��������� ����������� ������������� Android-����������
opennet.ru
Open sourceDownload an early look of the new Android Developer Console - Android Developer Console Help
support.google.com
Open sourceSee the full picture, correlated to your attack surface.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Related stories
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Google to Require App Verification for Android Sideloading with Power User Bypass
Google has announced a new policy requiring all Android apps installed outside the Google Play Store to undergo developer verification, aiming to curb the rise of malware and scam campaigns exploiting sideloading. The company cited increasingly aggressive online threats and the use of social engineering tactics that prompt users to bypass existing security warnings, leading to the installation of malicious applications. Under the new system, unverified apps will be blocked from installation on Google-certified devices, with the goal of making it harder for threat actors to distribute harmful software. In response to backlash from users and developers concerned about the impact on Android's openness, Google has stated that it will provide an exemption mechanism for "experienced users" or power users, though the specifics of this bypass have not yet been finalized. The move represents a balancing act between enhancing platform security and maintaining the flexibility that has traditionally set Android apart. Google has previously faced criticism for similar restrictions and appears to be adjusting its approach to address both security and user autonomy concerns.
Jun 29, 2026
Android Tightens Sideloading With Developer Verification ‘Accountability Layer’
Google is preparing an Android change that adds an **“Accountability Layer”** to sideloaded (third‑party) apps, introducing a higher-friction installation flow intended to make users acknowledge the risks rather than banning sideloading outright. Google’s Matthew Forsythe said advanced users will still be able to proceed via an *Install without verifying* option, while Android’s developer verification requirements are being expanded, including a new account type aimed at students and hobbyists that can distribute apps with limited reach without completing full verification. The move aligns with continued growth in Android malware distributed via sideloaded APKs, which threat researchers report remains a primary infection vector despite protections like **Google Play Protect**. Kaspersky reported preliminary 2025 data showing Android threat detections rising by nearly half, with Q3 detections up **38%** versus Q2 and sharp growth in **trojan banker** activity; attackers commonly deliver malicious APKs through messaging apps (often using deceptive filenames like `party_pics.jpg.apk`) and then propagate further via victims’ contact lists, with search-engine spam and email lures also used to drive installs outside official app stores.
Jun 29, 2026
Google Adds 24-Hour Delay for Sideloading Unverified Android Apps
Google detailed a new **24-hour waiting period** for Android users who want to install apps from **unverified developers**, part of a broader sideloading policy change tied to developer identity verification. The new *advanced flow* requires users to enable **Developer Mode** and then wait before bypassing app verification, a design Google says is intended to disrupt **social engineering** scams that pressure victims into installing malicious APKs immediately. Google framed the delay as a safeguard for users whose phones hold sensitive personal and financial data, while still preserving a path for experienced users to take what it calls an informed risk. Google introduced the exception after backlash to its earlier plan to require verified developer accounts for apps on certified Android devices, including criticism from power users and civil society groups that objected to the identity verification requirement and associated fee. Reporting indicates the bypass can be enabled through a one-time process, and users who want unrestricted sideloading can select an **indefinite** option rather than waiting each time. The change does not eliminate Google's verification regime, but it creates a compromise that keeps sideloading available while adding friction specifically aimed at malware delivery campaigns that rely on urgency and coercion.
Jun 29, 2026