Protect sample privacy
Before submitting an APK, confirm that your team may share it and understand the platform rules for sample storage and visibility.
Independent retesting guide
How to retest APK detection results
Independent checks with third-party multi-engine platforms before and after hardening can help teams record changes and decide whether more investigation is needed.
- 1Confirm the APK SHA-256
- 2Submit or query it on a compliant third-party platform
- 3Keep the scan time and engine verdicts
- 4Use signing and device behavior to decide next steps
Compare like with like
Compare only APKs with the same business version, signing, and known configuration so unrelated changes are not attributed to hardening.
Finish with release validation
A scan result is a signal, not a final decision. Validate installation, critical flows, and destination-channel requirements too.
Validate a minimum profile with a real candidate
This is a guide to an external scan workflow. It does not mean the website provides VirusTotal or other third-party scanning services.
Questions
Understand the boundaries before configuring
Does the website upload APKs to VirusTotal automatically?
No. The website does not provide online VirusTotal upload or scanning.
Can a scan result decide whether to release?
No. Complete real-device testing, signing validation, and channel-specific checks as well.
Ready to start?