apk-scanner.com
DMSS
com.mm.android.DMSS · Build 2.6.22
Analysis: complete. Static analysis completed for this build. A grade is not a guarantee of safety. Historical verification does not establish current reachability.
- Grade / score
- D · 48/100
- Finding categories
- 8
- Occurrences
- 10
- Scanned
- 2026-10-09T15:56:48.223Z
- Document issued
- 2026-10-13T18:40:14.053Z
- Historical verifications
- 0
Finding evidence
Open a category to review its occurrences. Printing includes all categories and occurrences.
Firebase Cloud Messaging legacy server key · high · 1 occurrence
Remove the hard-coded credential from the app package, rotate/revoke it immediately, and move the secret to a backend the app calls with per-user authentication.
CWE-798 · MASVS-STORAGE-1
•••••••• (40+ chars, redacted)
Hardcoded HTTP Basic-auth credentials · high · 1 occurrence
Remove the hard-coded credential from the app package, rotate/revoke it immediately, and move the secret to a backend the app calls with per-user authentication.
CWE-798 · MASVS-STORAGE-1
Basic ••••••:•••••••• (redacted)
Private key material (third-party library artifact, shared across 3 unrelated developers) · low · 1 occurrence
Never ship private-key material in a client. Revoke/rotate the compromised key and hold it server-side or in a hardware-backed store.
CWE-321 · MASVS-CRYPTO-2
-----BEGIN PRIVATE KEY----- (redacted)
Google API key (client-shipped; restriction unverified) · low · 3 occurrences
Restrict the API key (application + API restrictions in Google Cloud Console); a client-shipped key is public, so restriction is the control.
CWE-798 · MASVS-STORAGE-1
AIza•••••••• (21–40 chars, redacted)AIza•••••••• (21–40 chars, redacted)AIza•••••••• (21–40 chars, redacted)
Firebase Storage bucket reference · low · 1 occurrence
Confirm the bucket/database denies anonymous read (enable auth / storage rules / RLS), then audit its contents for data already exposed while it was open.
CWE-200 · CWE-284 · MASVS-STORAGE-2
████████████
Background location access with advertising SDKs present · low · 1 occurrence
Justify background location; request foreground-only where possible and disclose the use in the Play Data Safety form.
CWE-359 · MASVS-PRIVACY-1
background location + ad SDKs
Cleartext (HTTP) traffic permitted · medium · 1 occurrence
Set android:usesCleartextTraffic=false and/or a networkSecurityConfig that forbids cleartext; serve all endpoints over HTTPS.
CWE-319 · MASVS-NETWORK-1
android:usesCleartextTraffic="true"
Short signing key (RSA 1024-bit) · medium · 1 occurrence
Use an RSA key of at least 2048 bits or an EC P-256 key for signing.
CWE-326 · MASVS-CRYPTO-1
RSA-1024
Control coverage
Mapped static evidence does not establish a control pass. Manual assessment remains separate.
| Control | Requirement | Recorded status |
|---|---|---|
| MASVS-STORAGE-1 | The app securely stores sensitive data. | Review signal |
| MASVS-STORAGE-2 | The app prevents leakage of sensitive data. | Review signal |
| MASVS-CRYPTO-1 | The app employs current strong cryptography and uses it according to best practices. | Review signal |
| MASVS-CRYPTO-2 | The app performs key management according to best practices. | Review signal |
| MASVS-AUTH-1 | The app uses secure authentication and authorization protocols. | Manual assessment |
| MASVS-AUTH-2 | The app performs local authentication securely. | Manual assessment |
| MASVS-AUTH-3 | The app secures sensitive operations with additional authentication. | Manual assessment |
| MASVS-NETWORK-1 | The app secures all network traffic according to current best practices. | Review signal |
| MASVS-NETWORK-2 | The app verifies the identity of the remote endpoint (e.g. certificate pinning). | No static findings · not a pass |
| MASVS-PLATFORM-1 | The app uses IPC mechanisms securely. | No static findings · not a pass |
| MASVS-PLATFORM-2 | The app uses WebViews securely. | No static findings · not a pass |
| MASVS-PLATFORM-3 | The app uses the user interface securely. | Manual assessment |
| MASVS-CODE-1 | The app requires an up-to-date platform version. | No static findings · not a pass |
| MASVS-CODE-2 | The app has a mechanism for enforcing updates. | Manual assessment |
| MASVS-CODE-3 | The app only uses software components without known vulnerabilities. | No static findings · not a pass |
| MASVS-CODE-4 | The app validates and sanitizes all untrusted inputs and follows secure-coding practice. | No static findings · not a pass |
| MASVS-RESILIENCE-1 | The app validates the integrity of the platform. | Manual assessment |
| MASVS-RESILIENCE-2 | The app implements anti-tampering mechanisms. | Manual assessment |
| MASVS-RESILIENCE-3 | The app implements anti-static-analysis mechanisms. | Manual assessment |
| MASVS-RESILIENCE-4 | The app implements anti-dynamic-analysis techniques. | Manual assessment |
| MASVS-PRIVACY-1 | The app minimizes access to sensitive data and resources. | Review signal |
| MASVS-PRIVACY-2 | The app prevents identification of the user. | No static findings · not a pass |
| MASVS-PRIVACY-3 | The app is transparent about data collection and usage. | No static findings · not a pass |
| MASVS-PRIVACY-4 | The app offers user control over their data. | Manual assessment |
Build identity and signature
- Scan ID
- 8571c630-061a-40d3-92f9-ac1d6ce1d932
- APK SHA-256
4b3578ec3b61dbbf5bcf1cf51e018ba0b76bb4ae1196f1abbc7e1e638168f2e4- Capsule SHA-256
27c91d4d695310c367450ffdad12109337d04328f7db36cb204f21c6371bc9e7- Signing key
- IE6LeZNX4dAAPLGr
Verify the signed JSON at apk-scanner.com/verify. This printed view is a presentation of the signed record; the JSON is the verification artifact.