Android 17 Blocks Non-Accessibility Apps from Accessibility API to Prevent Malware Abuse
好的,我现在需要帮用户总结一篇文章,控制在100字以内。首先,我得仔细阅读文章内容,理解主要信息。 文章主要讲的是Google在测试Android 17 Beta 2中的新安全功能,作为Advanced Protection Mode的一部分。这个功能阻止非辅助类应用使用辅助服务API,以防止恶意软件窃取数据。同时,还提到了新的联系人选择器功能。 接下来,我要提取关键点:Android 17测试新安全功能,限制非辅助应用使用API,保护隐私;新增联系人选择器,提升用户体验。这些信息需要简洁明了地表达出来。 然后,我得确保语言流畅,符合用户的要求,不使用特定的开头词。最后检查字数是否在限制内。 </think> Google测试Android 17新安全功能,限制非辅助类应用使用辅助服务API以防止数据窃取,并新增联系人选择器提升用户体验。 2026-3-16 05:43:0 Author: thehackernews.com(查看原文) 阅读量:5 收藏

Mobile Security / Data Protection

Android Accessibility API Security

Google is testing a new security feature as part of Android Advanced Protection Mode (AAPM) that prevents certain kinds of apps from using the accessibility services API.

The change, incorporated in Android 17 Beta 2, was first reported by Android Authority last week.

AAPM was introduced by Google in Android 16, released last year. When enabled, it causes the device to enter a heightened security state to guard against sophisticated cyber attacks. Like Apple's Lockdown Mode, the opt-in feature prioritizes security at the cost of diminished functionality and usability so as to minimize the attack surface.

Some of the core configurations include blocking app installation from unknown sources, restricting USB data signaling, and mandating Google Play Protect scanning.

"Developers can integrate with this feature using the AdvancedProtectionManager API to detect the mode's status, enabling applications to automatically adopt a hardened security posture or restrict high-risk functionality when a user has opted in," Google noted in its documentation outlining Android 17's features.

The latest restriction added to the one-tap security setting aims to prevent apps that are not classified as accessibility tools from being able to leverage the operating system's accessibility services API. Verified accessibility tools, identified by the isAccessibilityTool="true" flag, are exempted from this rule.

According to Google, only screen readers, switch-based input systems, voice-based input tools, and Braille-based access programs are designated as accessibility tools. Antivirus software, automation tools, assistants, monitoring apps, cleaners, password managers, and launchers do not fall under this category.

While AccessibilityService has its legitimate use cases, such as assisting users with disabilities in using Android devices and apps, the API has been extensively abused by bad actors in recent years to steal sensitive data from compromised Android devices.

With the latest change, any non-accessibility app that already has the permission will have its privileges automatically revoked when AAPM is active. Users will also not be able to grant apps permissions to the API unless the setting is turned off.

Android 17 also comes with a new contacts picker that allows app developers to specify only the fields they want to access from a user's contact list (e.g., phone numbers or email addresses) or allow users to select certain contacts with a third-party app.

"This grants your app read access to only the selected data, ensuring granular control while providing a consistent user experience with built-in search, profile switching, and multi-selection capabilities without having to build or maintain the UI," Google said.

Found this article interesting? Follow us on Google News, Twitter and LinkedIn to read more exclusive content we post.


文章来源: https://thehackernews.com/2026/03/android-17-blocks-non-accessibility.html
如有侵权请联系:admin#unsafe.sh