An attacker does not need you to open the app. They do not even need to hide code in it. It is enough that it gets installed.
Bitdefender Labs has documented an Android flaw that sends a phone into an endless loop: after installation, a core system service crashes, restarts, reads the same file again and crashes again. Rebooting does not help. Safe mode does not help, because the crash happens before safe mode takes effect. What remains is a factory reset — which erases everything on the device.
The researchers call it GhostMap, and it is not a bug in any particular app. It is a disagreement about how to read an APK. An APK is a ZIP archive, and ZIP records sizes in several places without requiring them to agree. Two Android libraries check those records differently. libziparchive validates the declared uncompressed length only for entries stored without compression. libandroidfw instead asks whether an entry is deflated, treats everything else as stored, and maps it into memory at the declared size. An entry whose method field is neither stored nor deflate falls into exactly that gap: one library never checks, the other trusts.
The rest is mechanics. Android maps the file rather than copying it, and the kernel permits a mapping larger than the file. The first time a process reads past the real end, the access faults and the process dies with a SIGBUS. In Bitdefender's reproduction, an 8,408-byte APK was mapped across roughly 16 megabytes, and the fault landed about 197,000 bytes past the end of the file.
Whether the phone sees a single crash or the loop depends on which file inside the app was malformed. A broken manifest makes the installation fail, leaving nothing behind. A malformed resource that a system service parses automatically while walking the list of installed apps hits system_server, the process that hosts most of Android. From install to first crash took about a second; in one capture the cycle repeated 110 times while the screen stayed on the boot animation.
Bitdefender ran into the problem on 12 August 2026, when a banking dropper APK collected from the wild crashed its analysis emulators. The malware had been wrapped by a packer that also broke the ZIP structure — nothing suggests the author intended that. The persistent version was built by the researchers; it has not been seen in the wild.
They reported on 20 August and, after further testing, on 25 August. Google closed the first report as not reproducible and said the second fell outside the scope of a security update, referring it to a feature team for possible inclusion in a future version. The researchers push back with a precedent: in 2016 Google rated a weaker variant, CVE-2016-6724, as Moderate even though it too required a factory reset, and by today's published severity guidelines a persistent service disruption would be High.
The paper lays out several abuse scenarios, explicitly as hypotheticals: disabling a phone and using the threat of a factory reset as extortion leverage; making a malicious app impossible to remove by malforming its own icon so the launcher, the settings app list and the app info screen all crash before they can draw the uninstall button; and blinding security scanners, because the same parsing code runs inside inspection tools and a native SIGBUS is not a Java exception anyone can catch.
Defence today is detection, not patching. The malformation is visible in the file's structure before installation, and Bitdefender Mobile Security flags it as Android.Riskware.Ghostmap.rA. A third-party app cannot block an installation — Android's security model forbids it. Bitdefender says every version from Android 10 up is affected, reproduced on a Pixel 10 running Android 17 with the 5 August 2026 security patch.
What to watch: whether Google tightens the check in libandroidfw, whether the issue surfaces in a monthly bulletin — and whether scanners start rejecting unknown ZIP method fields instead of interpreting them.




