GhostMap: a no-permission app traps Android in a boot loop
Bitdefender details GhostMap, an Android flaw where a malformed APK sends system_server into an endless crash loop. Google plans no security patch.

On 5 November 2026 Bitdefender published its research on GhostMap, an Android flaw that lets an installed app push the device into a continuous crash loop. The demonstration app contains no executable code, requests no permissions and does not even need to be opened: installing it is enough. The story was reported by BleepingComputer, Help Net Security and Infosecurity Magazine, which agree on the main points.
According to Bitdefender, Google has known about the issue since August but does not plan a security update, and the flaw has no CVE identifier. Bitdefender, quoted by Help Net Security, has not observed the technique being used in real attacks.
How it was found
It started with a malware sample. According to Help Net Security, on 12 August a banking trojan dropper collected in the wild crashed Bitdefender’s analysis emulators during installation. The sample had been processed with a packer, a tool that rewrites an APK’s internal structure to hinder reverse engineering, and that rewrite also broke the Android installer. Looking into the behaviour, the researchers concluded that the problem was not the malware itself but a flaw in the operating system.
Technical details
An APK is a ZIP archive. Each entry in the archive declares a compression method and an uncompressed size. Android handles two methods, stored (uncompressed) and deflated, but the method field is 16 bits wide and can hold other values too.
According to the description reported by Help Net Security, two Android libraries interpret that field differently:
- the first checks the declared size only for stored entries;
- the second treats anything that is not deflated as stored and maps the file into memory at the declared size.
An entry with a third method value therefore passes both checks. The kernel allows a mapping larger than the file: in Bitdefender’s capture an 8,408-byte APK was mapped across about 16 MB. The first read past the real end of the file triggers a SIGBUS, the signal the processor uses to stop a process accessing invalid memory, and the reading process dies.
Which process crashes depends on the malformed file. If it is the manifest, the installer crashes. If it is a resource that system_server (the process hosting most Android services) reads automatically after installation, the crash repeats at every restart, because the service rereads the same file each time.
The Pixel 10 test
The researchers reproduced the loop on a Pixel 10 running Android 17 with the 5 August 2026 security patch. According to BleepingComputer the crash sequence started about one second after installation and repeated 110 times in normal boot and 72 times in safe mode, which therefore offers no way out.
Bitdefender told Help Net Security that the flaw is in base Android code (AOSP) and that it was verified from Android 10 up to the latest version; phones from other manufacturers were not tested. The sources differ on recovery: Infosecurity Magazine reports that the only way out is a factory reset, which erases local data; BleepingComputer adds deleting the malformed file via ADB, which only works if USB debugging was already enabled and the command runs before the next crash.
Possible abuse described by Bitdefender
According to Infosecurity Magazine, Bitdefender outlines some theoretical scenarios:
- bricking a phone for extortion, with a malformed resource read by system_server;
- an app that cannot be removed: a malformed icon crashes the launcher, the app list in Settings and the app’s own info screen when the user tries to uninstall it;
- disabling security tools: mobile security apps, sandboxes and automated analysis pipelines use Android’s code to read resources and can be crashed by the file they are examining;
- delivery through an update: the app is harmless at first download and the malformed file arrives later.
On the last point Bitdefender does not say whether Google Play review would stop such a file, and told Help Net Security it would not go into detail. In MITRE ATT&CK for Mobile terms, the scenarios map to Endpoint Denial of Service (T1642) and, for analysis tools, to Impair Defenses (T1629).
Google’s response
Bitdefender reported the issue on 20 August and the report was closed as “Won’t Fix (Not Reproducible)”. On 25 August it sent an extended version with a working proof of concept: according to Help Net Security, Google judged it outside the scope of a security fix and passed it to a team for possible inclusion in a future version. Bitdefender said it informed Google of the publication date at the end of October and Google agreed. BleepingComputer asked Google about the fix status and had received no reply at the time of publication.
What it means for organisations
There is no patch and, according to Bitdefender, third-party security apps can warn but lack the permissions to block an installation. The only useful moment to stop the attack is before the APK is installed. For a fleet of corporate or BYOD smartphones the risk is mainly to availability: a locked device can only be recovered with a reset, losing any data not stored elsewhere. For NIS2 entities and healthcare organisations using Android devices on wards or in the field, it is a business continuity issue more than a confidentiality one.
What to do now
- Restrict app sources: use device management (MDM/Android Enterprise) to block installs from unknown sources and allow only approved apps.
- Check updates of approved apps, not just the first install, given the delayed-delivery scenario.
- Static analysis of APKs: Bitdefender stresses that the malformation is visible in the file structure without installing or running it; its product detects it as
Android.Riskware.Ghostmap.rA. In sandboxes and analysis pipelines, expect tools based on Android code to crash on the sample. - Back up device data and keep a procedure ready for factory reset and fast reprovisioning.
- Follow Android security bulletins: as of today GhostMap has neither an announced fix nor a CVE.
Last updated:


