Adversaries may use screen capture to collect additional information about a target device, such as applications running in the foreground, user data, credentials, or other sensitive information. Applications running in the background can capture screenshots or videos of another application running in the foreground by using the Android
MediaProjectionManager (generally requires the device user to grant consent). Background applications can also use Android accessibility services to capture screen contents being displayed by a foreground application. An adversary with root access or Android Debug Bridge (adb) access could call the Android
Monokle can record the screen as the user unlocks the device and can take screenshots of any application in the foreground. Monokle can also abuse accessibility features to read the screen to capture data from a large number of popular applications.
TrickMo can use the
|M1013||Application Developer Guidance||
Application developers can apply the
Enterprise policies should block access to the Android Debug Bridge (ADB) by preventing users from enabling USB debugging on Android devices unless specifically needed (e.g., if the device is used for application development). An EMM/MDM can use the Android
Users should be advised not to grant consent for screen captures to occur unless expected. Users should avoid enabling USB debugging (Android Debug Bridge) unless explicitly required.
|ID||Data Source||Data Component|
|DS0041||Application Vetting||API Calls|
|DS0042||User Interface||System Settings|
The user can view a list of apps with accessibility service privileges in the device settings. Application vetting services can look for the use of the Android
MediaProjectionManager class, applying extra scrutiny to applications that use the class.