File scan report
Verdict Safe
Is app- release (3). apk safe? Yes, no threats found.
74 engines report no detections on a medium-prevalence Android APK with no sandbox or host-reputation hits.
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
The file can be considered safe for normal use; continue monitoring for any future engine detections or developer updates.
Good practice2 tips
We found nothing harmful in this file.
Install it only from Google Play or the developer's own website.
Keep your security software and system updates switched on.
No scanner can promise a file is 100% safe.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 65 flagged
- Flagged 0
- No detection 65
- No result 9
- Code signing Not applicable
- Test run Completed
- First seen 3mo ago
Chapter 02
Why we think so
1 point against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Zero malicious detections across 74 reporting engines and no sandbox verdict. The single rule-based trigger notes direct-IP traffic but explicitly requires further correlation. One unconfirmed user report suggested malicious, yet no review decision exists.
The complete absence of malicious engine detections across major, smaller, and less reliable engines outweighs the single rule-based flag. One of our behaviour rules itself cautions that direct-IP traffic occurs in legitimate installers and must be correlated with host reputation, which returned zero malicious hosts. Medium prevalence and 14-day age indicate the file is neither nor extremely rare. No external-intel or similar-hash corroboration exists to support a malicious classification.
What We Detected
74 antivirus engines scanned the APK; none returned a malicious or suspicious result. Behaviour analysis recorded 15 direct-IP connections and three MITRE techniques common in legitimate software but zero offensive techniques and no sandbox verdicts.
Threat Behavior
The rule-based rule one of our behaviour rules fired because the sample contacted IPs without recording an application domain. The rule text states this pattern alone is inconclusive and must be weighed against host reputation, which showed zero known-malicious hosts among the inspected addresses.
What To Do Now
Keep security software enabled. If the APK originates from an official store or trusted developer channel, the current evidence supports safe use. Re-scan after any future updates or if additional context (source URL, developer signature) becomes available.
Where this verdict could be wrong1 caveat
- recentFeedback[0].suggestedVerdict=malicious from one user report, though reviewDecision is still null
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero malicious detections across 74 reporting engines
- No sandbox malicious verdict
- Zero known-malicious contacted hosts
- Direct-IP traffic without recorded domain (rule only)
6 sources checked · 5 complete · 1 partial. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 3sandbox rule tags
- 0spawned processes
- 16network contacts
- 4filesystem & mutex artifacts
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Techniques observed in the sandbox
3MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1071· Application protocol
- T1406
- T1573
Observed activity
Network contacts
1616 hosts, listed as 15 addresses, 1 link. Links show the host and path only.
- IP address
172.64.149.246 - IP address
104.26.13.205 - IP address
185.199.108.133 - IP address
173.194.194.94 - IP address
172.67.151.52 - IP address
173.194.193.113
Show all 16 entries for network contacts
- IP address
173.194.206.147 - IP address
172.217.113.4 - IP address
185.199.109.133 - IP address
104.18.38.10 - IP address
172.217.115.4 - IP address
173.194.64.139 - IP address
172.217.119.4 - IP address
142.250.125.95 - IP address
142.251.157.119 - URL
https://dqyggtrgbcgjnlnbgjfr.supabase.co/rest/v1/user_sessions
Files
4Files the file created, changed or deleted.
- Written
/data/misc/profiles/cur/0/com.animeze.app/primary.prof - Written
/data/user/0/com.animeze.app/files/profileinstaller_profileWrittenFor_lastUpdateTime.dat - Written
/data/user/0/com.animeze.app/shared_prefs/animeze_settings.xml - Deleted
/data/user/0/com.animeze.app/shared_prefs/animeze_settings.xml.bak
Chapter 04
Technical details
None of the 65 antivirus engines that checked it flag it.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Aug 7, 2026, 4:28 AM UTC
- SHA-256
9f7cb97327778ea5d4069842073110e87585010633ea3cb593b62b71d0a4e48f- SHA-1
ce9ce494f409e7990e9d0f81d343bbed6d5b108c- MD5
1080cbec7e2ea029e692e656c50a2bfe
About this file
app-release (3).apk is an Android file of 24.4 MB.
- Type and size
- Android · 24.4 MB
- Signer
- Not applicable
- First seen
- Jul 23, 2026On VirusTotal.
- Submitted by
- 5 distinct sourcesRarely seen: few people have submitted this exact file.
First scanned Updated
Antivirus consensus
0 of 65 engines flagged this file
9 of the 74 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-117 engines0flagged
- Tier-236 engines0flagged
- Low-trust12 engines0flagged
View all 74 engine results
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudNo result
- ALYacClean
- Antiy-AVLClean
- APEXNo result
- ArcabitClean
- AvastClean
- Avast-MobileClean
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxClean
- BkavClean
- CAT-QuickHealClean
- ClamAVNo result
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceNo result
- CynetClean
- DrWebClean
- ElasticNo result
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusNo result
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoNo result
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightClean
- TACHYONClean
- tehtrisNo result
- TencentClean
- TrapmineNo result
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookClean
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is app-release (3).apk safe?
What is app-release (3).apk?
How many antivirus engines detected app-release (3).apk?
What is the SHA-256 hash of app-release (3).apk?
Is it safe to install app-release (3).apk?
How up to date is this analysis of app-release (3).apk?
Community
Member reviews and reports for this exact file hash.