Browse appsScan report

Turbo Fax: send fax from phone

Piksoft Inc. · Build 1.0.13

com.piksoft.turbofax
Historical result · coverage unknownScanned 2026-09-02 11:07 UTC

Review the recorded findings below. An overall grade is withheld where required checks lack coverage; a new scan may provide additional evidence.

Overview

Review needed

1 high or critical finding category to review

Turbo Fax: send fax from phone (com.piksoft.turbofax) was scanned at version 1.0.13 on 2026-09-02 but is not graded, because the analysis did not complete enough of its checks for a score to mean anything. It has 1 high or critical finding among 5 finding categories across 8 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.

Finding categories58 occurrences
High / critical1Category count
Tracking SDKs5Presence, not observed traffic
Historical score37 / 100Grade D · qualified by coverage

Start with these findings

highPrivate key material3 occurrences

Interpretation & review guidance

A complete PEM private-key block is embedded in the app. This is a real finding worth review — but it is often a bundled library test/sample key rather than a production secret, so we flag it high and leave confirmation to you (a bare header alone no longer triggers it).

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.
mediumShort signing key (RSA 1024-bit)1 occurrence

Interpretation & review guidance

The signing key is shorter than the modern 2048-bit RSA minimum. Short keys are cryptographically weaker; a release should re-key to at least RSA-2048 (or an EC key).

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 Realtime Database reference1 occurrence

Interpretation & review guidance

A Firebase Realtime Database URL. Nearly every app that uses Firebase ships one. It's only an exposure if the database rules are world-readable — that's what live verification checks.

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.
View all 5 categories

Privacy

14 requested permissions · 2 flagged high-risk classes.

Review privacy signals →

Build & components

51 components recorded. Certificate parsing does not validate APK signature integrity.

Inspect build evidence →

Findings

5 categories · 8 occurrences. Severity totals describe categories. Expand a finding for interpretation and review guidance.

highPrivate key material3 occurrences

Interpretation & review guidance

A complete PEM private-key block is embedded in the app. This is a real finding worth review — but it is often a bundled library test/sample key rather than a production secret, so we flag it high and leave confirmation to you (a bare header alone no longer triggers it).

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
repack/org/bouncycastle/openssl/test/data/rsa/openssl_rsa_unencrypted.pem
Recorded match
Pattern recorded; identifying value redacted.

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 tools

Search recorded evidence and save private review notes with Pro. $99/month plus applicable tax.

mediumShort signing key (RSA 1024-bit)1 occurrence

Interpretation & review guidance

The signing key is shorter than the modern 2048-bit RSA minimum. Short keys are cryptographically weaker; a release should re-key to at least RSA-2048 (or an EC key).

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
Signing metadata
Representative location
META-INF/signing:key
Recorded match
RSA-1024

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 tools

Search recorded evidence and save private review notes with Pro. $99/month plus applicable tax.

lowFirebase Realtime Database reference1 occurrence

Interpretation & review guidance

A Firebase Realtime Database URL. Nearly every app that uses Firebase ships one. It's only an exposure if the database rules are world-readable — that's what live verification checks.

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.

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 tools

Search recorded evidence and save private review notes with Pro. $99/month plus applicable tax.

lowFirebase Storage bucket reference2 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
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
Pattern recorded; identifying value redacted.

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 tools

Search 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)

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 tools

Search recorded evidence and save private review notes with Pro. $99/month plus applicable tax.

Privacy signals

Capabilities and bundled software do not prove that data was collected or transmitted.

Requested permissions14
Flagged high-risk classes2
Detected SDKs5

Camera Storage

Requested permission inventory (14)
  • android.permission.ACCESS_NETWORK_STATE
  • android.permission.CAMERA
  • android.permission.INTERNET
  • android.permission.POST_NOTIFICATIONS
  • android.permission.READ_EXTERNAL_STORAGE
  • android.permission.RECEIVE_BOOT_COMPLETED
  • android.permission.VIBRATE
  • android.permission.WAKE_LOCK
  • android.permission.WRITE_EXTERNAL_STORAGE
  • com.android.vending.BILLING
  • com.google.android.c2dm.permission.RECEIVE
  • com.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICE
  • com.google.android.gms.permission.AD_ID
  • com.piksoft.turbofax.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION

Data collection & flow (privacy signal, not part of the grade)

Data the app can access
Camera
Camera
Photos & files
Storage (write)
Persistent identifiers (referenced in code)
Advertising ID (AAID)Android IDDevice ID / IMEI
Where it can go
Third parties present (4)
Google AdMobGoogle AdServicesGoogle Firebase AnalyticsGoogle Tag Manager
  • 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, 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 is not conclusive because analysis coverage is incomplete or unknown.

Trackers & SDKs (5 detected · privacy signal, not part of the grade)

Advertising
Google AdMobGoogle AdServices
Analytics
Google Firebase AnalyticsGoogle Tag Manager
Crash reporting
Google Crashlytics

Build & components

Scanned build 1.0.13. Store metadata may describe a newer release.

APK SHA-256149977004c965e14e318b4c373d8788b140f855379216ea5eedffca8af00afeb

Signing certificate (who signed this build — factual, not part of the grade)

Signer
Piksoft Inc. self-signed
Scheme
V2V1
Key
RSA 1024-bit
Algorithm
sha1WithRSA
Validity
2014-03-26 → 2114-03-02
Cert SHA-256
43:78:c2:02:a2:d3:67:a2:5c:0a:eb:95:25:a2:35:62:ef:eb:ee:b6:b3:1a:a1:ed:bf:03:13:95:12:56:3c:c8

The certificate fingerprint identifies the parsed signing certificate. Knowing this public fingerprint does not establish ownership or validate the APK signature.

Signature integrity: not established by certificate parsing.

Component inventory

51 components. Advisory matching covers a curated set; no match is not proof that a component is vulnerability-free.

Bundled components and recorded advisory matches
ComponentVersionAdvisory matches
androidx.activity:activity1.6.0None recorded
androidx.annotation:annotation-experimental1.3.0None recorded
androidx.appcompat:appcompat1.6.1None recorded
androidx.appcompat:appcompat-resources1.6.1None recorded
androidx.arch.core:core-runtime2.1.0None recorded
androidx.browser:browser1.4.0None recorded
androidx.cardview:cardview1.0.0None recorded
androidx.coordinatorlayout:coordinatorlayout1.1.0None recorded
androidx.core:core1.10.1None recorded
androidx.core:core-ktx1.10.1None recorded
androidx.cursoradapter:cursoradapter1.0.0None recorded
androidx.customview:customview1.1.0None recorded
androidx.customview:customview-poolingcontainer1.0.0None recorded
androidx.databinding:viewbinding8.7.2None recorded
androidx.datastore:datastore1.0.0None recorded
androidx.datastore:datastore-preferences1.0.0None recorded
androidx.documentfile:documentfile1.0.0None recorded
androidx.drawerlayout:drawerlayout1.1.1None recorded
androidx.dynamicanimation:dynamicanimation1.0.0None recorded
androidx.emoji2:emoji21.2.0None recorded
androidx.emoji2:emoji2-views-helper1.2.0None recorded
androidx.exifinterface:exifinterface1.3.7None recorded
androidx.fragment:fragment1.3.6None recorded
androidx.interpolator:interpolator1.0.0None recorded
androidx.legacy:legacy-support-core-utils1.0.0None recorded
androidx.lifecycle:lifecycle-livedata2.0.0None recorded
androidx.lifecycle:lifecycle-livedata-core2.5.1None recorded
androidx.lifecycle:lifecycle-process2.4.1None recorded
androidx.lifecycle:lifecycle-runtime2.5.1None recorded
androidx.lifecycle:lifecycle-viewmodel2.5.1None recorded
androidx.lifecycle:lifecycle-viewmodel-savedstate2.5.1None recorded
androidx.loader:loader1.0.0None recorded
androidx.localbroadcastmanager:localbroadcastmanager1.0.0None recorded
androidx.percentlayout:percentlayout1.0.0None recorded
androidx.preference:preference1.1.0None recorded
androidx.print:print1.0.0None recorded
androidx.recyclerview:recyclerview1.3.1None recorded
androidx.savedstate:savedstate1.2.0None recorded
androidx.startup:startup-runtime1.1.1None recorded
androidx.tracing:tracing1.0.0None recorded
androidx.transition:transition1.2.0None recorded
androidx.vectordrawable:vectordrawable1.1.0None recorded
androidx.vectordrawable:vectordrawable-animated1.1.0None recorded
androidx.versionedparcelable:versionedparcelable1.1.1None recorded
androidx.viewpager2:viewpager21.1.0-beta02None recorded
androidx.viewpager:viewpager1.0.0None recorded
com.google.android.material:material1.9.0None recorded
com.squareup.okhttp3:okhttp4.11.0None recorded
kotlinx:coroutines_android1.6.4None recorded
kotlinx:coroutines_core1.6.4None recorded
kotlinx:coroutines_play_services1.6.4None recorded
Export SBOM
About this app · store information

About this app

The easiest way to scan and fax from phone (or fax existing PDFs).

Content ratingEveryone
Download size16.7 MB
Privacy policyPublished →
Developer sitewww.turboscanapp.com

Screenshots

App screenshotApp screenshotApp screenshotApp screenshotApp screenshot

Scan history

Each row is an observed scan. Gaps between scans do not establish how long a finding existed.

Scanned (UTC)BuildScoreGrade
2026-09-02 11:07 UTC1.0.1337D
2026-09-01 10:06 UTC1.0.1343D

View changes between the last two scans →

Export & share

Exports describe the recorded assessment. Signed evidence proves origin and integrity, not completeness or safety.

Coverage & gap matrix · Verify signed evidence

API users can request authenticated, scan-specific exports at /v1/scans/8faa5a00-4ce9-44d3-baa0-7106bcb8ae80/findings.sarif (also coverage.json and proof.json).

Request a correction or removal · How to interpret a scan · Browse apps