Is app-release (3).apk safe?
74 engines report no detections on a medium-prevalence Android APK with no sandbox or host-reputation hits.
Zero malicious detections across 74 reporting engines and no sandbox verdict. The single heuristic trigger notes direct-IP traffic but explicitly requires further correlation. One unconfirmed user report suggested malicious, yet no review decision exists.
9f7cb97327778ea5d4…b62b71d0a4e48fRecommended next actions
Before 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.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
Zero malicious detections across 74 reporting engines and no sandbox verdict. The single heuristic 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 tier-1, tier-2, and low-trust engines outweighs the single heuristic flag. The DirectIpC2 rule 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 brand-new 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 ambient MITRE techniques but zero offensive techniques and no sandbox verdicts.
Threat Behavior
The heuristic rule MalwareTips.Synth.DirectIpC2 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 endpoint protection 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 (heuristic only)
The file can be considered safe for normal use; continue monitoring for any future engine detections or developer updates.
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
Partial1 of 16 contacted hosts were cross-checked; coverage is incomplete.
YARA
Complete1 signature or behavior rule matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
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 - +1 more recorded observation in Analyst mode
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 - +1 more recorded observation in Analyst mode
5 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
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.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 1rule hit recorded
- 0 / 74engines flagged
- 5sources in submission history
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
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
- Aug 7, 2026, 4:28 AM 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.
- Recovery step 01
Install it only from Google Play, the developer's official store, or another source you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
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.