Is dokdo-1-4-2.apk safe?
Only 1 of 74 engines raised a generic low-trust alert, while established prevalence, runtime observations, and complete contacted-domain checks provide no corroborating threat evidence.
A lone low-trust engine applied a generic trojan label, while all contributing tier-1 engines remained silent. The APK has been broadly observed since 2019, and its completed sandbox run showed no offensive techniques, malicious assessment, known-malicious contacted domain, or malicious dropped child.
e84b45c25bdefba2d7…d1f2fee15e5aecRecommended 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.
A lone low-trust engine applied a generic trojan label, while all contributing tier-1 engines remained silent. The APK has been broadly observed since 2019, and its completed sandbox run showed no offensive techniques, malicious assessment, known-malicious contacted domain, or malicious dropped child.
Only MaxSecure flagged the sample among 74 engines, using a generic heuristic label rather than a named malware family. No tier-1 engine detected it, making the isolated alert much more consistent with a false positive. The APK has circulated across 266 sources and 332 submissions since 2019, providing substantial historical exposure. One completed sandbox run recorded common mobile application and advertising activity, with no offensive techniques or malicious sandbox assessment. All 14 distinct contacted domains were covered by the host-reputation check, and none were known malicious or suspicious. Obfuscation and anti-debugging tags warrant ordinary caution, but they lack independent malicious corroboration here.
What We Detected
MaxSecure was the only detector among 74 engines, assigning the generic label “Trojan.Malware.300983.susgen.” No tier-1 engine raised an alert, and there is no family consensus. The sample has also been submitted 332 times by 266 sources since June 2019, indicating extensive historical exposure.
Threat Behavior
One completed sandbox run recorded 13 techniques associated with ordinary mobile application activity and no offensive techniques. Contacts included Unity, Google Analytics, AppsFlyer, Facebook, and advertising infrastructure. The reputation check covered all 14 distinct contacted domains and found none known malicious or suspicious. Two dropped files were inspected without a malicious child finding, although their individual classifications remain unknown.
What To Do Now
Use an official or otherwise trusted distribution source and verify that the application identity and requested permissions match expectations. Keep Android security protections enabled, and avoid installation if the origin is unofficial or the app requests permissions unrelated to its purpose.
Where this verdict could be wrong3 caveats
- MaxSecure flags the file as 'Trojan.Malware.300983.susgen', but it is a lone generic detection from a low-trust engine with no tier-1 corroboration.
- The APK carries obfuscation, reflection, cryptography, native-code, anti-debugging, telephony, and GPS-related tags; these increase opacity but are not corroborated by offensive runtime behavior.
- The two dropped children remain individually unclassified even though droppedChildren.hasMaliciousChild=false.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- engines.tier1Malicious=0, with 15 tier-1 engines reporting no detection.
- Only 1/74 engines flagged the sample, and engines.onlyLowTrustFlagging=true.
- behaviour.offensiveCount=0 and behaviour.hasMaliciousSandboxVerdict=false.
- contactedHosts inspected all 14 distinct domains with zero malicious or suspicious matches.
- The file has 332 submissions from 266 sources dating back to 2019.
- MaxSecure produced the sole generic trojan detection among 74 engines.
- Static tags indicate obfuscation, reflection, cryptography, native code, anti-debugging checks, telephony access, and GPS checks.
- Two dropped children were inspected but remain individually unclassified.
- The application contacted advertising, analytics, and attribution services during execution.
Install only if obtained from a trusted source and its requested Android permissions are appropriate. Keep device security protections enabled and remove the app if it displays unexpected behavior.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial14 of 31 contacted hosts were cross-checked; coverage is incomplete.
YARA
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.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 13MITRE ATT&CK techniques
- 0spawned processes
- 32network contacts
- 6filesystem & mutex artifacts
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- config.uca.cloud.unity3d.com
- remote-config-prd.uca.cloud.unity3d.com
- www.google-analytics.com
- init.supersonicads.com
- cdp.cloud.unity3d.com
- prd-lender.cdp.internal.unity3d.com
- unity-data-gke-prd-gateway.cdp.internal.unity3d.com
- o-sdk.mediation.unity3d.com
- outcome.supersonicads.com
- t.appsflyer.com
- 64.233.166.188
- 172.253.63.101
- 34.111.113.40
- 3.167.37.18
- 34.107.172.168
- 216.239.38.223
- 142.251.143.174
- 108.138.192.12
- 13.226.175.123
- 108.156.2.38
- http://www.google-analytics.com/collect
- /data/data/com.zzoo.dokdo/shared_prefs/com.zzoo.dokdo.v2.playerprefs.xml
- /data/user/0/com.zzoo.dokdo/shared_prefs/com.zzoo.dokdo.v2.playerprefs.xml
- /data/user/0/com.zzoo.dokdo/shared_prefs/Mediation_Shared_Preferences.xml
- /data/data/com.zzoo.dokdo/shared_prefs/com.zzoo.dokdo.v2.playerprefs.xml.bak
- /data/user/0/com.zzoo.dokdo/shared_prefs/com.zzoo.dokdo.v2.playerprefs.xml.bak
- /data/user/0/com.zzoo.dokdo/shared_prefs/Mediation_Shared_Preferences.xml.bak
Files this sample writes at runtime
This file drops 2 children at runtime. None are currently flagged malicious in our cache.
- 48dd9171400c34017a38…1fcfd1Never scannednever seen before
- 8337212354871836e676…6e1015Never 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
- 1 / 74engines flagged
- 266sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
The hash has a long, established submission history across 266 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 02
1 of 74 antivirus engines flagged the file, including MaxSecure.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 332 times from 266 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: dokdo-1-4-2.apk — e84b45c25bdefba2d743d3b314b6199e7b6ba1e7918ae6994cd1f2fee15e5aec
ProvenanceObservedSourceUploaded fileObserved at - 05
File written: com.zzoo.dokdo.v2.playerprefs.xml — /data/data/com.zzoo.dokdo/shared_prefs/com.zzoo.dokdo.v2.playerprefs.xml
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: com.zzoo.dokdo.v2.playerprefs.xml — /data/user/0/com.zzoo.dokdo/shared_prefs/com.zzoo.dokdo.v2.playerprefs.xml
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Contacted host: config.uca.cloud.unity3d.com — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: remote-config-prd.uca.cloud.unity3d.com — 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.
YARA rules
No matchesThe rule pass completed without a saved public match.
1 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
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- dokdo-1-4-2.apk
- Format
- Android
- Code signing
- Not applicable to this file type
- Size
- 30.5 MB
- Last analyzed
- Sep 27, 2026, 2:48 PM UTC
e84b45c25bdefba2d743d3b314b6199e7b6ba1e7918ae6994cd1f2fee15e5aecSafety & 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 dokdo-1-4-2.apk safe?
What is dokdo-1-4-2.apk?
How many antivirus engines detected dokdo-1-4-2.apk?
What is the SHA-256 hash of dokdo-1-4-2.apk?
Is it safe to install dokdo-1-4-2.apk?
How up to date is this analysis of dokdo-1-4-2.apk?
Community
Member reviews and reports for this exact file hash.