Our call: Is app-release (3).apk safe?Safe
Zero engine detections, clean runtime behaviour, and medium prevalence indicate a benign Android application.
- 0 of 74 antivirus engines flagged the file.Observed · Antivirus analysis
- No completed runtime observation is available for this file.Derived · Runtime coverage
- The hash has been submitted 6 times from 5 sources.Derived · Saved report facts
9f7cb97327778ea5d4…71d0a4e48fBefore installing
Install it only from Google Play, the developer's official store, or another source you independently trust.
If you already installed it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 engines flagged the file.
Sandbox
PartialRuntime data is present, but no completed sandbox environment is recorded.
Network
Complete1 contacted host was cross-checked.
YARA
Complete1 signature or behavior rule matched.
External intel
Complete3 of 3 independent reference sources completed.
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
app-release (3).apk
9f7cb97327778ea5d4069842073110e87585010633ea3cb593b62b71d0a4e48f
01Uploaded file
Files
Created or changed
- Written fileObserved
primary.prof
/data/misc/profiles/cur/0/com.animeze.app/primary.prof
02Isolated runtime analysis - Written fileObserved
profileinstaller_profileWrittenFor_lastUpdateTime.dat
/data/user/0/com.animeze.app/files/profileinstaller_profileWrittenFor_lastUpdateTime.dat
03Isolated runtime analysis
Network
Hosts contacted
- Contacted hostObserved
172.64.149.246
Contact observed during runtime.
04Isolated runtime analysis - Contacted hostObserved
104.26.13.205
Contact observed during runtime.
05Isolated runtime analysis
5 recorded facts from one runtime window. Every fact remains independently traceable in the evidence ledger below.
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 74 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
No completed runtime observation is available for this file.
ProvenanceDerivedSourceRuntime coverageObserved at - 03
The hash has been submitted 6 times from 5 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: app-release (3).apk — 9f7cb97327778ea5d4069842073110e87585010633ea3cb593b62b71d0a4e48f
ProvenanceObservedSourceUploaded fileObserved at - 05
File written: primary.prof — /data/misc/profiles/cur/0/com.animeze.app/primary.prof
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: profileinstaller_profileWrittenFor_lastUpdateTime.dat — /data/user/0/com.animeze.app/files/profileinstaller_profileWrittenFor_lastUpdateTime.dat
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Contacted host: 172.64.149.246 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: 104.26.13.205 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Intelligence
The complete saved assessment, kept intact and grounded in the scan evidence.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
All 74 engines returned clean results with no tier-1 or low-trust malicious flags. Behavioural analysis shows no offensive techniques or malicious host contacts, and external intelligence sources report no hits.
The complete absence of malicious detections across 74 engines, including 17 tier-1 engines, strongly supports a clean classification. Runtime behaviour is limited to ambient techniques with no offensive MITRE indicators or malicious sandbox verdicts. The single heuristic trigger for direct-IP traffic is explicitly caveated by the rule itself as potentially benign. Medium prevalence with multiple submitters over a single day aligns with a newly released legitimate application rather than malware distribution.
What We Detected
74 antivirus engines scanned the APK with zero malicious detections. Behavioural monitoring recorded three ambient techniques and direct-IP connections to 15 addresses, but no offensive MITRE techniques or malicious host reputation matches.
Threat Behavior
No sandbox verdicts flagged the sample as malicious. The application wrote typical Android profile and preference files without persistence mechanisms or dropped children. External intelligence sources (CIRCL, MalwareBazaar, YARAify) returned no matches.
What To Do Now
The file can be installed and executed with standard caution. Monitor for unusual battery or data usage after installation, as with any newly released application.
Where this verdict could be wrong1 caveat
- Direct-IP traffic to 15 addresses without recorded domains could indicate C2 infrastructure, but the heuristic rule itself notes this pattern also occurs in legitimate installers.
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 engine detections across all tiers
- No offensive MITRE techniques observed
- Medium prevalence consistent with legitimate new release
The evidence supports treating this APK as safe for normal use; continue monitoring for any post-installation anomalies.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime behavior was not available
The report does not treat a missing runtime observation as a clean result.
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence172.64.149.246 · 104.26.13.205 · 185.199.108.133
0 of 74 engines flagged this file
View all 74 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- app-release (3).apk
- Format
- Android
- Code signing
- Not applicable to this file type
- Size
- 23.3 MB
- Last analyzed
- Jul 24, 2026, 2:25 PM UTC
9f7cb97327778ea5d4069842073110e87585010633ea3cb593b62b71d0a4e48fSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
Install it only from Google Play, the developer's official store, or another source you independently trust.
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
- app-release (3).apk appears safe. 0 of 74 antivirus engines flagged it. Install it only from Google Play, the developer's official store, or another source you independently trust.
- app-release (3).apk is an Android app (APK), about 23.3 MB. Our analysis did not identify a verdict-driving threat signal. A file's name can be reused by different files, so we identify it by its cryptographic hash (below).
- None — 0 of 74 antivirus engines flagged app-release (3).apk. That's reassuring, though it is not proof that a file is safe, so we also weigh its behaviour, identity, and reputation.
- The SHA-256 hash of app-release (3).apk is 9f7cb97327778ea5d4069842073110e87585010633ea3cb593b62b71d0a4e48f, and its MD5 is 1080cbec7e2ea029e692e656c50a2bfe. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
- Based on the recorded evidence, app-release (3).apk has a low observed risk. The important caveat is source: make sure you downloaded it from the official website or a trusted store, because attackers sometimes distribute malware-laced copies under a legitimate file's name. If your own antivirus flags it, verify the source and the exact hash before overriding the warning.
- This report reflects the scan run on July 24, 2026. Because a file's hash never changes, the identity of app-release (3).apk is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.