Bazuka Android Malware Fakes Your Screen to Hide Theft, and Uses AI to Pick Victims
Researchers at Dutch mobile security firm ThreatFabric have detailed a previously unknown Android malware framework called Bazuka. They found it in late October 2026 while investigating an NFC-relay banking Trojan. ThreatFabric describes it as a full framework: a dropper or downloader, a core component, and 23 modules covering overlays, keylogging, 2FA and SMS interception, remote control, and crypto-address swapping.
The most unusual feature is a new overlay technique. The malware can capture a screenshot of the home screen or lock screen and display it on demand, covering up malicious activity running in the background. The operator control panel also includes AI chat, supporting both locally hosted models and models accessed through an API. A sample prompt refers to a score, suggesting operators can ask the AI to rank victims by how attractive they are as targets.
The dropper apps appear to spread through at least two channels: traffers using social media ads or bogus sites, and the Google Play Store. One dropper poses as a premium, adult-friendly version of TikTok. Once the core and modules load, Bazuka acts as a keylogger and classic overlay trojan, showing a fake screen at the right moment. The core abuses Android accessibility services and Android Debug Bridge (ADB) commands to grant itself permissions, can enable Wireless Debugging, and disables Google Play's protection component. It can also wipe its own data and disable itself.
The malware has not been attributed to any known actor, though the panel mixes English and Russian. ThreatFabric warns that ADB bridging is becoming standard in banking trojans and could let malware deploy independent modules that survive removal of the host app. Separately, Zimperium reported ArcticRAT, another Android threat with 129 commands that uses LLM APIs to process stolen SMS and app data.
Why it matters
Bazuka's screenshot overlay breaks the assumption that what a user sees on screen reflects what the device is doing, so staff may not notice an active compromise of banking or crypto apps. Its abuse of accessibility services and Wireless Debugging, plus disabling Google Play's protection, means a Play Store listing and built-in scanning are not enough assurance. Businesses with staff using personal or unmanaged Android phones for banking, 2FA or SMS codes are most exposed.
What to do
- Review which Android apps hold accessibility service permissions and remove any that do not clearly need them.
- Check devices for Developer options or Wireless Debugging enabled without a known reason.
- Treat unexpected apps posing as premium versions of known brands, such as com.tiktok.premium, as suspicious and remove them.
- Avoid installing apps from ads, social media links or third-party sites.