Adblock Browser: Fast & Secure
eyeo GmbH · Build 3.12.1
Static checks identify review items, not a guarantee of safety.
Overview
4 finding categories to review
Adblock Browser: Fast & Secure (org.adblockplus.browser) scored grade A, 96 out of 100, in a static scan of version 3.12.1 on 2026-10-08. It has no high or critical findings, and 4 lower-severity finding categories across 24 occurrences. 5 tracking SDKs are present in the package, which describes what ships, not what runs or what it sends. This is static analysis of a single build: it does not observe the app running and does not establish that any data is exposed.
Start with these findings
lowData Safety label omits Contacts1 occurrence
Interpretation & review guidance
The app's Google Play Data Safety label omits a data category it can actually access — a permission it requests, or an advertising/device identifier it references. Under-declaring collection is a Play policy issue and a COPPA/privacy concern. This is a static signal: a requested permission is capability, not proof of collection — confirm against runtime behavior.
How often Data Safety labels disagree with the package →
- Evidence
- 1 recorded occurrence in the analyzed APK. These are distinct stored findings, not a count of every source match.
- Verification
- Static detection; current reachability is not established.
lowExported content provider with path-restricted permissions (third-party library artifact, shared across 8 unrelated developers)2 occurrences
Interpretation & review guidance
An exported content provider declares no permission. Other apps on the device may reach it — verify it enforces access control internally; this flags the attack surface, not a confirmed leak.
- Evidence
- 2 recorded occurrences in the analyzed APK. These are distinct stored findings, not a count of every source match.
- Verification
- Static detection; current reachability is not established.
lowFirebase Storage bucket reference20 occurrences
Interpretation & review guidance
A Firebase Cloud Storage bucket reference (the default <project>.appspot.com). Storing user files here is normal — it's only an exposure if the Storage security rules allow public read/list, which live verification tests.
- Evidence
- 20 recorded occurrences in the analyzed APK. These are distinct stored findings, not a count of every source match.
- Verification
- Static detection; current reachability is not established.
Build & components
0 components recorded. Certificate parsing does not validate APK signature integrity.
Inspect build evidence →Findings
4 categories · 24 occurrences. Severity totals describe categories. Expand a finding for interpretation and review guidance.
lowData Safety label omits Contacts1 occurrence
Interpretation & review guidance
The app's Google Play Data Safety label omits a data category it can actually access — a permission it requests, or an advertising/device identifier it references. Under-declaring collection is a Play policy issue and a COPPA/privacy concern. This is a static signal: a requested permission is capability, not proof of collection — confirm against runtime behavior.
How often Data Safety labels disagree with the package →
- Evidence
- 1 recorded occurrence in the analyzed APK. These are distinct stored findings, not a count of every source match.
- Verification
- Static detection; current reachability is not established.
Evidence preview
- Evidence type
- Static string match
- Representative location
data-safety:Contacts- Recorded match
Pattern recorded; identifying value redacted.
1 recorded findings have inspectable metadata. Duplicate matches may share a representative location.
Review whether this belongs to intended app functionality or a bundled library. A static match does not establish runtime impact.
Preview evidence and Pro toolsSearch recorded evidence and save private review notes with Pro. $99/month plus applicable tax.
lowExported content provider with path-restricted permissions (third-party library artifact, shared across 8 unrelated developers)2 occurrences
Interpretation & review guidance
An exported content provider declares no permission. Other apps on the device may reach it — verify it enforces access control internally; this flags the attack surface, not a confirmed leak.
- Evidence
- 2 recorded occurrences in the analyzed APK. These are distinct stored findings, not a count of every source match.
- Verification
- Static detection; current reachability is not established.
Evidence preview
- Evidence type
- Parsed app configuration
- Representative location
AndroidManifest.xml:um.chrome.browser.provider.ChromeBrowserProvider- Recorded match
ChromeBrowserProvider (exported, some paths guarded)- Detector rule
manifest- Recorded file locations
AndroidManifest.xml:um.chrome.browser.provider.ChromeBrowserProvider
2 recorded findings have inspectable metadata. Duplicate matches may share a representative location.
Review whether this belongs to intended app functionality or a bundled library. A static match does not establish runtime impact.
Preview evidence and Pro toolsSearch recorded evidence and save private review notes with Pro. $99/month plus applicable tax.
lowFirebase Storage bucket reference20 occurrences
Interpretation & review guidance
A Firebase Cloud Storage bucket reference (the default <project>.appspot.com). Storing user files here is normal — it's only an exposure if the Storage security rules allow public read/list, which live verification tests.
- Evidence
- 20 recorded occurrences in the analyzed APK. These are distinct stored findings, not a count of every source match.
- Verification
- Static detection; current reachability is not established.
Evidence preview
- Evidence type
- Static string match
- Representative location
lib/arm64-v8a/libchrome.so- Recorded match
Pattern recorded; identifying value redacted.- Detector rule
firebase_storage_bucket- Recorded file locations
lib/arm64-v8a/libchrome.so
20 recorded findings have inspectable metadata. Duplicate matches may share a representative location.
Review whether this belongs to intended app functionality or a bundled library. A static match does not establish runtime impact.
Preview evidence and Pro toolsSearch recorded evidence and save private review notes with Pro. $99/month plus applicable tax.
lowGoogle API key (client-shipped; restriction unverified)1 occurrence
Interpretation & review guidance
Android apps are designed to ship Google API keys in the client; Google restricts them by app signing certificate + enabled API. This is only a problem if the key is left unrestricted — presence alone is expected, not an exposure.
- Evidence
- 1 recorded occurrence in the analyzed APK. These are distinct stored findings, not a count of every source match.
- Verification
- Static detection; current reachability is not established.
Evidence preview
- Evidence type
- Static string match
- Representative location
resources.arsc- Recorded match
AIza•••••••• (21–40 chars, redacted)- Detector rule
google_api_key- Recorded file locations
resources.arsc
1 recorded findings have inspectable metadata. Duplicate matches may share a representative location.
Review whether this belongs to intended app functionality or a bundled library. A static match does not establish runtime impact.
Preview evidence and Pro toolsSearch recorded evidence and save private review notes with Pro. $99/month plus applicable tax.
No categories match these filters. Clear the search or choose all severities.
Privacy signals
Capabilities and bundled software do not prove that data was collected or transmitted.
Precise location Approx. location Camera Microphone Contacts Accounts Storage List installed apps
Requested permission inventory (53)
Data collection & flow (privacy signal, not part of the grade)
- Approximate location, Precise location requested while 1 ad/attribution SDK(s) are present (Google AdMob) — location commonly feeds ad targeting.
- Persistent-identifier APIs referenced in code (Advertising ID (AAID), Android ID, Device ID / IMEI) with 4 analytics/ad SDK(s) present — the mechanism used for cross-app profiling.
- Camera, Contacts, Microphone, Personal info, Photos & files data requested with third-party analytics/ad SDKs present.
This maps what the app can access (permissions it requests, identifier APIs its code references) to the third parties bundled in it. It reflects capability and SDK presence — not proof that a specific value was transmitted.
Data Safety: declared vs observed (Play label vs our analysis)
We compare the developer's Google Play Data Safety declaration with what the binary can actually do (permissions it requests, identifier APIs and third-party SDKs it ships). A mismatch is a capability signal to confirm — a requested permission is not proof of collection.
Trackers & SDKs (5 detected · privacy signal, not part of the grade)
Build & components
Scanned build 3.12.1. Store metadata may describe a newer release.
9f19e8b9f62b4b5bad1493d7ece8d219e1fc538d43bbe9250d152d0df99567c2Signing certificate (who signed this build — factual, not part of the grade)
7b:ed:00:40:28:ba:e3:cb:58:05:d1:0d:1b:f5:ec:07:31:e3:7a:94:10:ec:1a:c9:59:da:50:fa:2f:ca:d4:c4The certificate fingerprint identifies the parsed signing certificate. Knowing this public fingerprint does not establish ownership or validate the APK signature.
Component inventory
No bundled components detected by this scan.
Export SBOMAbout this app · store information
About this app
Surf the web without annoying ads. Adblock Browser is fast, fair and secure
Screenshots
Scan history
Each row is an observed scan. Gaps between scans do not establish how long a finding existed.
| Scanned (UTC) | Build | Score | Grade |
|---|---|---|---|
| 2026-10-08 02:51 UTC | 3.12.1 | 96 | A |
| 2026-10-01 02:51 UTC | 3.12.1 | 96 | A |
| 2026-09-22 23:18 UTC | 3.12.1 | 96 | A |
| 2026-09-12 02:05 UTC | 3.12.1 | 96 | A |
| 2026-09-09 19:37 UTC | 3.12.1 | Not graded | Not graded |
Export & share
Exports describe the recorded assessment. Signed evidence proves origin and integrity, not completeness or safety.
Coverage & gap matrix · Verify signed evidence
Embed the latest grade
Embed this grade
The badge reads the latest recorded grade each time it is loaded, and links back to the full report so a reader can see the build it covers and what the scan could not see.
Grades can move when a new version is scanned or when a detector is corrected. If you would rather publish a grade that cannot change under you, link a signed Proof Capsule instead.
API users can request authenticated, scan-specific exports at /v1/scans/8dcb2417-00f8-4503-8d59-b952dc042ed0/findings.sarif (also coverage.json and proof.json).
Request a correction or removal · How to interpret a scan · Browse apps