A Single Install Is Enough to Break the Phone

Bitdefender Labs published a flaw called GhostMap on 5 November 2026 that lets a specially built Android app put a phone into a permanent crash and restart loop. The app needs no permissions, carries no executable code and does not have to be opened, because installing it is enough. Bitdefender says it affects Android 10 and later and reproduced it on a Pixel 10 running Android 17 with the 5 August 2026 security patch. The loop started about one second after installation and repeated 110 times in normal mode and 72 times in safe mode, so safe mode does not help.

The cause is a disagreement between two Android libraries that read ZIP files. For an entry whose compression method is neither stored nor deflated, one library skips the size check and the other maps the file at the declared size. Reading past the real end of the file crashes the process that touches it, and when that process is a core system service the phone cannot finish booting.

Google Closed the Report, Then Reopened It

Google has not shipped a fix, and its position moved twice before the public write-up.

Date (2026)What happened
12 AugustBitdefender finds the issue while a banking trojan crashes its analysis emulators
20 AugustFirst report to Google, closed as Won't Fix (Not Reproducible)
25 AugustExpanded report with a persistent crash-loop demonstration
5 NovemberBitdefender publishes; Google still treats it as outside a security update
9 NovemberBitdefender reports Google reopened the case and raised the severity to High

Bitdefender stresses that a higher severity is not a patch and gives no release date. It has seen no use of the loop against real victims, and BleepingComputer, which reported the same facts, was still waiting for Google's answer on fix status.

What to Change in Your Device Policy

The only realistic point of defence is the install itself. Bitdefender notes that third-party security apps can warn about the file but cannot block an installation or remove another app. Recovery is a factory reset that erases local data, or deleting the file over ADB, which works only if USB debugging was already on and only before the next crash.

For a company fleet that means three checks this week: confirm that device policy blocks installs from unknown sources, confirm that company data is backed up off the phone, and decide who owns a phone that needs a reset in the field. Do not switch on USB debugging across the fleet as a fix, because that trades one risk for another.