AI translator: Camera & Voice
Amobear Application - AILABS. · Build v2.0.0_20261006
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: 2 unauthenticated read checks against backends referenced in this build — 2 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
AI translator: Camera & Voice (com.translator.languagetranslate.translateAI) scored grade B, 92 out of 100, in a static scan of version v2.0.0_20261006 on 2026-11-13. It has no high or critical findings, and 3 lower-severity finding categories across 4 occurrences. 20 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
mediumCleartext (HTTP) traffic permitted1 occurrence
Interpretation & review guidance
The manifest permits cleartext (HTTP) traffic. Data sent over plain HTTP can be read or tampered with on the network; modern apps should require HTTPS.
Remediation: How to fix cleartext (HTTP) traffic in an Android app →
Reference: CWE-319 · MASVS-NETWORK-1 — 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 reference1 occurrence
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
- 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.
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?
The findings above are counts. The app's developer can see each one in context, be told when a new build changes the result, and re-check any backend that answers. Verify that you control amobear.com (the site on this app's Play listing) to open that view. Free; no card.
Build & components
1 components recorded. Certificate parsing does not validate APK signature integrity.
Inspect build evidence →Findings
3 categories · 4 occurrences. Severity totals describe categories. Expand a finding for interpretation and review guidance.
mediumCleartext (HTTP) traffic permitted1 occurrence
Interpretation & review guidance
The manifest permits cleartext (HTTP) traffic. Data sent over plain HTTP can be read or tampered with on the network; modern apps should require HTTPS.
Remediation: How to fix cleartext (HTTP) traffic in an Android app →
Reference: CWE-319 · MASVS-NETWORK-1 — 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
- Parsed app configuration
- Representative location
AndroidManifest.xml- Recorded match
android:usesCleartextTraffic="true"- Detector rule
manifest- Recorded file locations
AndroidManifest.xml
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 reference1 occurrence
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
- 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
Pattern recorded; identifying value redacted.- Detector rule
firebase_storage_bucket- 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.
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
classes4.dex- Recorded match
AIza•••••••• (21–40 chars, redacted)- Detector rule
google_api_key- Recorded file locations
classes4.dex
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.
Camera Microphone Draw over other apps
Requested permission inventory (20)
Data collection & flow (privacy signal, not part of the grade)
- Persistent-identifier APIs referenced in code (Advertising ID (AAID), Android ID, Device ID / IMEI) with 17 analytics/ad SDK(s) present — the mechanism used for cross-app profiling.
- Camera, Microphone, 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 comparison not recorded.
Trackers & SDKs (20 detected · privacy signal, not part of the grade)
Build & components
Scanned build v2.0.0_20261006. Store metadata may describe a newer release.
0a2c055068f29101ba83fbe77d93393156a40ae56adaae495ab8576f9fea1e6fSigning certificate (who signed this build — factual, not part of the grade)
1a:d6:68:d5:b3:a0:be:8d:fa:4d:00:7a:b5:ca:90:56:c0:28:41:88:cd:6c:c2:b8:6d:36:2b:04:be:a9:fd:19The 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 | 4.12.0 | None recorded |
About this app · store information
About this app
Camera translator, translate voice, photo and text with AI language translator.
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-13 18:00 UTC | v2.0.0_20261006 | 92 | B |
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/e938c536-904b-4cfa-af5b-4385845708fe/findings.sarif (also coverage.json and proof.json).
Request a correction or removal · How to interpret a scan · Browse apps