earnify
BP Products North America Inc · Build 5.18.1
Rescanning re-reads this build; it does not re-check any backend referenced inside it.
Static checks identify review items, not a guarantee of safety.
Backend checks: 4 unauthenticated read checks against backends referenced in this build — 4 refused access. Each check describes one request at the recorded scan time and does not establish the backend's current state.
Overview
3 finding categories to review
earnify (com.bp.app.bpme.global.ros) scored grade A, 97 out of 100, in a static scan of version 5.18.1 on 2026-11-12. It has no high or critical findings, and 3 lower-severity finding categories across 6 occurrences. 10 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 Location1 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 →
Remediation: How to fill out Google Play Data Safety accurately →
Reference: CWE-359 · MASVS-PRIVACY-3 — what the control asks for, and other apps with the same finding.
- 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.
lowFirebase Storage bucket reference3 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.
Remediation: Fix a publicly readable Firebase database →
Reference: CWE-200 · CWE-284 · MASVS-STORAGE-2 — what the control asks for, and other apps with the same finding.
- Evidence
- 3 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.
lowGoogle API key (client-shipped; restriction unverified)2 occurrences
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.
Remediation: How to store secrets in a mobile app (without hardcoding) →
Reference: CWE-798 · MASVS-STORAGE-1 — what the control asks for, and other apps with the same finding.
- 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.
Is this your app?
This app's Play listing has no developer site, so there's no domain to check. Email security@apk-scanner.com from the developer address shown on Google Play.
Build & components
1 components recorded. Certificate parsing does not validate APK signature integrity.
Inspect build evidence →Findings
3 categories · 6 occurrences. Severity totals describe categories. Expand a finding for interpretation and review guidance.
lowData Safety label omits Location1 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 →
Remediation: How to fill out Google Play Data Safety accurately →
Reference: CWE-359 · MASVS-PRIVACY-3 — what the control asks for, and other apps with the same finding.
- 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:Location- 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.
lowFirebase Storage bucket reference3 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.
Remediation: Fix a publicly readable Firebase database →
Reference: CWE-200 · CWE-284 · MASVS-STORAGE-2 — what the control asks for, and other apps with the same finding.
- Evidence
- 3 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
resources.arsc- Recorded match
Pattern recorded; identifying value redacted.- Detector rule
firebase_storage_bucket- Recorded file locations
resources.arsc
3 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)2 occurrences
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.
Remediation: How to store secrets in a mobile app (without hardcoding) →
Reference: CWE-798 · MASVS-STORAGE-1 — what the control asks for, and other apps with the same finding.
- 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
- Static string match
- Representative location
resources.arsc- Recorded match
AIza•••••••• (21–40 chars, redacted)- Detector rule
google_api_key- Recorded file locations
resources.arsc
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.
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
Requested permission inventory (23)
Data collection & flow (privacy signal, not part of the grade)
- Approximate location, Precise location requested while 2 ad/attribution SDK(s) are present (Google AdMob, AppsFlyer) — location commonly feeds ad targeting.
- Persistent-identifier APIs referenced in code (Advertising ID (AAID), Android ID, Device ID / IMEI +3 more) with 8 analytics/ad SDK(s) present — the mechanism used for cross-app profiling.
- Camera 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 (10 detected · privacy signal, not part of the grade)
Build & components
Scanned build 5.18.1. Store metadata may describe a newer release.
eddb20f2b0a72a35d6d591a15f9f49c5a7b964caa58c6a621195c89c0443062eSigning certificate (who signed this build — factual, not part of the grade)
fa:55:8b:0a:40:7d:0e:04:8c:ea:12:ac:e5:be:f6:38:2f:a8:8e:50:26:95:83:c1:22:ba:72:c0:01:94:4a:91The certificate fingerprint identifies the parsed signing certificate. Knowing this public fingerprint does not establish ownership or validate the APK signature.
Component inventory
1 components. Advisory matching covers a curated set; no match is not proof that a component is vulnerability-free.
| Component | Version | Advisory matches |
|---|---|---|
com.squareup.okhttp3:okhttp | 5.1.0 | None recorded |
About this app · store information
About this app
Save on gas and convenience with the earnify™ App
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-11-12 07:43 UTC | 5.18.1 | 97 | A |
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/bce16581-e4aa-4469-8014-679216528181/findings.sarif (also coverage.json and proof.json).
Request a correction or removal · How to interpret a scan · Browse apps