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.
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
3 events from the most recent confirmed update back to the earliest known activity.
Google plans phased regional rollout of sideloading changes
Google said the new sideloading verification changes are expected to roll out during 2026 on a regionally phased basis, so availability will differ by location. The move was presented as part of broader efforts to reduce Android fraud, scams, and malware risks.
Android announces higher-friction sideloading verification flow
Android announced an 'Accountability Layer' for third-party app installation that adds warnings and a more difficult sideloading flow rather than banning sideloading outright. Google said advanced users will still be able to choose an 'Install without verifying' option.
Google outlines new Play developer verification requirements
Google described new developer verification requirements on the Android Developers Blog, citing rising fraud, scams, and malware on digital platforms. The policy also introduced a limited-distribution account type for students and hobbyist developers.
Related entities
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
Sources
2 references tracked. Mallory keeps watching after this page renders.
See 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
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
Apple and Google Tighten Mobile App Controls Through Telemetry and Sideloading Limits
Apple introduced **Personalized Collections** in the App Store, a recommendation feature built on detailed user telemetry that researchers at Mysk said logs every tap, app usage pattern, downloads, and potentially behavioral signals such as typing speed. The researchers reported that this analytics collection cannot be disabled and that related records appear in Apple account data exports from `privacy.apple.com`, prompting criticism over the granularity of the data and the lack of an opt-in model for personalization. Google separately outlined a stricter Android sideloading process called **Advanced Flow** for apps from unverified developers, adding several barriers including developer mode activation, anti-coaching checks, a device restart with reauthentication, biometric or PIN confirmation, and a mandatory 24-hour waiting period. Google said internet-sideloaded apps are linked to far higher malware rates than Play-distributed apps and plans to deliver the controls through Google Play Services, but the move has also raised concerns that the company is using security justifications to further centralize control over how users discover and install mobile apps.
Jun 29, 2026