1. Establish provenance
Use a publisher channel you can verify independently, rather than a chain of redirects or a forwarded chat attachment. Check the exact domain spelling. HTTPS protects a connection, but it does not certify that the operator is the app’s genuine publisher.
2. Compare Android identity
Android packages have an application identifier and are signed. A developer can use a signing-key upgrade, so interpretation must follow genuine publisher information. A mismatch that nobody can explain is a reason to stop; a familiar icon is not an alternative identity check.
Android’s signing documentation explains the role of certificates in updates. A signature by itself is not a safety rating. It identifies a signing key, which must still be linked to the right publisher.
3. Understand checksums
SHA-256 can tell you whether two copies have identical bytes. Compare against a trusted release record, not merely another mirror repeating the same claim. A matching hash cannot prove that an app behaves safely or that its server protects your information.
4. Review permissions and warnings
- Keep Google Play Protect enabled and take security warnings seriously.
- Do not provide SMS access, accessibility control or remote screen access just because a download page requests it.
- A request for banking credentials or an OTP outside the genuine service is a serious warning sign.
- If permission purpose is unclear, stop and ask the verified publisher rather than guessing.
If you already installed a suspicious file
Stop using it and do not enter more credentials. Use Android’s security tools and Play Protect to review the device. From a trusted device or official app, secure affected accounts. If payment information was exposed, contact the relevant bank through its established channel. Do not pay a stranger for a promised “account unlock”.
No blanket safety badges
This site has not performed binary analysis, malware scanning or a device test on a Master or Gold old version. We therefore show no “100% safe”, fake antivirus result or fabricated download count.
Sources & scope
Sources checked 26 October 2026. General guidance is separate from app-specific verification; no APK in this project has been independently tested.