Is bad-banker-1-23.apk safe?
No engine flagged the 3,616-day-old Android APK across 77 scanners.
Zero detections from 77 engines, 11 of them tier-1, on a file first seen in 2016 with medium prevalence. No sandbox results, no malicious children, and no external-intel hits support a clean classification.
5756829898f4e7e940…9b89ac6e5aaf17Recommended 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 detections from 77 engines, 11 of them tier-1, on a file first seen in 2016 with medium prevalence. No sandbox results, no malicious children, and no external-intel hits support a clean classification.
The sample shows a complete absence of malicious detections across the entire engine set, including 11 tier-1 engines that returned clean. Its age and submission history indicate established distribution rather than a new threat. No runtime or no complete contacted-host reputation result was available signal, and external intelligence sources also report no hits.
What We Detected
77 engines scanned the APK; none returned a malicious or suspicious result. Eleven tier-1 engines explicitly classified it clean.
Threat Behavior
No sandbox execution data, no contacted domains or IPs, and the single dropped child file carries an unknown verdict with zero malicious detections. External sources (CIRCL, MalwareBazaar, YARAify) contain no matching records.
What To Do Now
The file can be treated as safe for normal use. Keep Android security features enabled and avoid sideloading unknown APKs in the future.
- Zero malicious detections across 77 engines
- Medium prevalence over 3,616 days
- No external intelligence hits
The evidence supports treating the APK as safe; continue normal device security practices.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 77 engines flagged the file.
Sandbox
PartialRuntime data is present, but no completed sandbox environment is recorded.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
CompleteRule evaluation completed with no recorded matches.
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
bad-banker-1-23.apk
5756829898f4e7e9404faad66f49f29ff5a57bbfe8382e74f59b89ac6e5aaf17
01Uploaded file
Files
Created or changed
- Written fileObserved
Cocos2dxPrefsFile.xml
/data/user/0/com.sirnic.badbanker/shared_prefs/Cocos2dxPrefsFile.xml
02Isolated runtime analysis - Dropped fileDerived
bf04d65e91b617d927d252e4ff9bc9b0bd5230935c9d46f13acd3da3ac7010c2
No child-file verdict was available.
03Dropped-file analysis - +1 more recorded observation in Analyst mode
3 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.
Files this sample writes at runtime
This file drops 1 child at runtime. None are currently flagged malicious in our cache.
- bf04d65e91b617d927d2…7010c2Never scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 0rule hits recorded
- 0 / 77engines flagged
- 11sources 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 77 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 14 times from 11 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: bad-banker-1-23.apk — 5756829898f4e7e9404faad66f49f29ff5a57bbfe8382e74f59b89ac6e5aaf17
ProvenanceObservedSourceUploaded fileObserved at - 05
File written: Cocos2dxPrefsFile.xml — /data/user/0/com.sirnic.badbanker/shared_prefs/Cocos2dxPrefsFile.xml
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Dropped file: bf04d65e91b617d927d252e4ff9bc9b0bd5230935c9d46f13acd3da3ac7010c2 — No child-file verdict was available.
ProvenanceDerivedSourceDropped-file 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.
YARA rules
No matchesThe rule pass completed without a saved public match.
0 of 77 engines flagged this file
View all 77 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
- bad-banker-1-23.apk
- Format
- Android
- Code signing
- Not applicable to this file type
- Size
- 17.7 MB
- Last analyzed
- Aug 7, 2026, 4:44 AM UTC
5756829898f4e7e9404faad66f49f29ff5a57bbfe8382e74f59b89ac6e5aaf17Safety & 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 bad-banker-1-23.apk safe?
What is bad-banker-1-23.apk?
How many antivirus engines detected bad-banker-1-23.apk?
What is the SHA-256 hash of bad-banker-1-23.apk?
Is it safe to install bad-banker-1-23.apk?
How up to date is this analysis of bad-banker-1-23.apk?
Community
Member reviews and reports for this exact file hash.