Plain Text, Plain Risks: Measuring HTTP Inclusion in Android WebViews at Scale
We measure cleartext HTTP usage in 189,779 Android apps and show how insecure WebView configurations enable attacks ranging from phishing to full app takeover.
While the widespread adoption of HTTPS and browser-based visual warnings for HTTP content has largely mitigated machine-in-the-middle (MitM) attacks on the traditional Web, the mobile ecosystem presents a different situation. Web content embedded via the Android WebView component commonly lacks these built-in visual security indicators and grants apps granular control over transport-layer security. This flexibility raises a critical question: does the mobile-Web ecosystem keep up with the advancements of the modern Web?
In this paper, we perform the first large-scale analysis of HTTP inclusion in WebViews across 189,779 Google Play apps. Despite Android’s default policy of blocking HTTP traffic, we find that 33.74% of apps explicitly opt out. Dynamic analysis of 35,000 apps reveals that 69.96% of apps that opt out also relax the Mixed Content Policy, and we observe active HTTP traffic in 2,790. The security impact of these configurations is severe. We identify high-profile apps with 10M+ installations vulnerable to attacks ranging from phishing to full app takeover. Furthermore, we identify a major ad library transmitting cleartext ads, exposing billions of users to MitM attacks. We conclude with a qualitative developer study revealing that insecure practices are frequently driven by the requirements of third-party ad libraries and misconceptions regarding WebView’s security configuration modes.
@inproceedings{plaintext_beer,
author = {Philipp Beer and Sebastian Roth and Martina Lindorfer and Marco Squarcina},
title = {{Plain Text, Plain Risks: Measuring HTTP Inclusion in Android WebViews at Scale}},
booktitle = {35th USENIX Security Symposium (USENIX Security 26)},
year = {2026},
address = {Baltimore, MD},
publisher = {USENIX Association},
month = aug
}