File scan report
Verdict Suspicious
Is ps4- emulator- update- apkod. apk safe? Treat it as suspicious.
Four of the 67 antivirus engines that checked it tag this Android package as riskware or a generic Trojan, while two sandbox runs finished clean and no contacted server is on our known-malicious list.
Why Suspicious? 4 antivirus engines flag it; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
Prefer the official store or the developer's own site for this app, and avoid third-party APK mirrors for it. If the package is already installed and shows ad pop-ups, redirects or unexpected permissions, uninstall it and run a security scan with protection left enabled.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't install it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete the APK file. If you need the app, get it from Google Play instead.
If you already installed it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumMobile malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from AndroidFind the bad app and clean your phone. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Antivirus results
4 of 67 flagged
- Flagged 4
- No detection 63
- No result 8
- Code signing Not applicable
- Test run Completed
- First seen 4y ago
Chapter 02
Why we think so
5 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Presented as an update for an emulator and circulating since September 2022, this Android package is flagged by a small set of engines as Android riskware or a generic Trojan, and its network traffic goes to advertising-measurement devices. Two sandbox runs finished without a malicious verdict and none of the inspected servers is known-bad, so the evidence is mixed rather than conclusive.
The detection picture is thin but not empty: four engines flag the package, including one high-reputation engine naming a generic Android Trojan and another describing it as Android riskware with adware characteristics. The labels do not agree on a single family, and the majority of engines that analysed the file found nothing. Evidence from the test run points the other way: the combined sandbox verdict was clean, nothing was injected into other processes, no files were dropped and no persistence was recorded. The observed network connections are advertising-measurement devices plus the download portal that distributed the package, and the host reputation check we do have found no known-malicious server among the inspected contacts. There is also no certificate to vouch for the publisher, no entry in public malware-sample databases or malware-specific rule sets, and nobody has inspected the package contents, so nothing balances the riskware labels on the benign side. That split — riskware/possibly unwanted software signals against a clean runtime and a long, wide distribution history — leaves the file neither confirmed malicious nor demonstrably harmless.
What We Detected
This is an Android application package of roughly 100 KB that describes itself as an update for an emulator. Four of the 67 antivirus engines that checked it in our network flagged it: one high-reputation engine labels it a generic Android Trojan, another calls it Android riskware with adware traits, a third reports an application-risk verdict, and a fourth returns only a bare "detected" result. The rest of the engines that analysed the file — 63 of them — returned nothing, and no single malware family is agreed on by the high-reputation engines.
Threat Behavior
In the sandbox runs the package behaved quietly: nothing was injected into other applications, no files were written out, no persistence mechanism and no scheduled tasks were recorded, and the combined sandbox verdict was clean. There were no high-risk techniques among the recorded mappings; the activity that was seen is the kind of network use common to ordinary apps. Outbound traffic went to advertising-measurement services and to the download portal that carried the package, and the connection histories show no known-malicious server among the contacts that were checked.
Distribution and Context
The package has been around since September 2022 and has been submitted by 168 distinct sources, which is consistent with a widely mirrored Android download rather than a targeted implant. Public malware-sample databases and malware-specific community rule sets have no entry for it, and the package carries no code signature to identify a publisher. We have not examined the package's internal contents, so the permissions it requests and the libraries it bundles are unchecked.
What This Means
The engines that object to this package describe riskware or potentially unwanted behaviour — aggressive advertising and tracking integrated into a repackaged app — rather than a payload that hides, persists and steals data, and the evidence from the test run did not show such activity. Equally, the riskware labels come from several sources, so the file should not be treated as trusted software from a known vendor.
What To Do Now
If you found this through a third-party APK site, get the app from an official store or the developer's own site instead. If it is already installed and you see unexpected ad pop-ups, browser redirects or unfamiliar permissions, uninstall it and run a mobile security scan. Leave Android's built-in app scanning and your security software switched on.
Where this verdict could be wrong3 caveats
- The combined sandbox verdict was clean, with no injected processes, no dropped files and no persistence indicators, which is not what a functioning Android trojan usually looks like.
- Only 4 of the 67 antivirus engines that checked it flagged the package and the wording is mostly generic (a bare 'Detected', 'AppRisk:Generisk', a generic Agent label), so part of the signal could be rule-based over-flagging of a repackaged app.
- The package has been circulating since September 2022 with 168 distinct submitters and no listing in public malware-sample databases or malware-specific community rule sets, which argues against an actively distributed payload.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Two sandbox runs finished with a clean combined verdict, with no process injection, no dropped files and no persistence recorded.
- The contacted-host check covered 31 hosts and found no known-malicious and no known-suspicious server.
- No entry in public malware-sample databases and no malware-specific community rules matched.
- Widely distributed since September 2022 across 168 distinct submitters — consistent with a mirrored popular download rather than a targeted implant.
- Four engines flag the package as Android riskware or a generic Trojan, including a high-reputation engine using a Trojan label.
- The package is distributed outside official app stores through a third-party APK download portal.
- It carries no code signature, so there is no publisher identity to check.
- Its network traffic includes advertising-measurement devices typical of ad-monetised repackaged apps.
- We have no inspection of the package contents, so its declared permissions and bundled libraries are unchecked.
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 2 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 2isolated sandbox runs
- 7sandbox rule tags
- 0spawned processes
- 30network contacts
- 0filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Used an unusual way to talk to a server.
Moderate concern: Contacted a server on an unusual network port.
Note: Talked to servers over the internet during the test run.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 3: FileSeen in the test run
ps4-emulator-update-apkod.apk
42afec64182235d9d45b0de319edebbe5627ce1f465f31e62db0682b2d23847b
Uploaded file
- 2
Network
Hosts contacted
- Evidence 2 of 3: Contacted hostWorked out from other results
apkod.com
Low-confidence suspicious report, not counted as evidence.
Contacted-host cross-check - Evidence 3 of 3: Contacted hostSeen in the test run
s.w.org
Contacted during the test run.
Test run - +1 more recorded observation
3 facts from the test run. See the full activity list.
What this file did when executed
This file was detonated in 2 sandboxes and its runtime behaviour was observed.
Sandbox verdicts
1- VT: CLEANclean
Techniques observed in the sandbox
7MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1071· Application protocol
- T1095· Custom network
- T1421
- T1447
- T1507
- T1571· Unusual port
- T1573
Observed activity
Network contacts
3030 hosts, listed as 10 domains, 20 addresses. Links show the host and path only.
- Domain
apkod.com - Domain
s.w.org - Domain
secure.quantserve.com - Domain
2kpixel.quantserve.com - Domain
global.px.quantserve.com - Domain
rules.quantcount.com
Show all 30 entries for network contacts
- Domain
d2fashanjl7d9f.cloudfront.net - Domain
pxl.qccerttest.com - Domain
pixel.quantserve.com - Domain
a.nel.cloudflare.com - IP address
104.21.48.10 - IP address
172.67.175.179 - IP address
108.177.126.95 - IP address
108.177.127.95 - IP address
173.194.69.138 - IP address
142.251.31.95 - IP address
91.228.74.206 - IP address
52.222.139.5 - IP address
13.227.219.26 - IP address
35.190.80.1 - IP address
142.250.153.95 - IP address
142.250.145.188 - IP address
142.250.145.103 - IP address
142.250.145.99 - IP address
74.125.143.188 - IP address
64.233.171.188 - IP address
142.250.145.104 - IP address
142.250.152.188 - IP address
108.177.126.100 - IP address
108.177.126.113
Sandbox background — not the file
1The analysis machine's own processes and connections, recorded in every run.
- VM host
dns.google
Servers this file contacts
Some hosts this file contacts have only older or low-confidence reports in our URL scanner. They are shown for context and are not counted as evidence.
- apkod.comlow-confidence suspicious, risk 38
Chapter 04
Technical details
4 of the 67 antivirus engines that checked it flag it.
Sources checked
Every check behind this verdict
6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 4
- Ikarus (major engine)Trojan.AndroidOS.Agent
- BitDefenderFalxAndroid.Riskware.Nitol.B
- GoogleDetected
- SymantecMobileInsightAppRisk:Generisk
File fingerprint
- Last analyzed
- Nov 9, 2026, 1:49 PM UTC
- SHA-256
42afec64182235d9d45b0de319edebbe5627ce1f465f31e62db0682b2d23847b- SHA-1
e8ca94899149a999aa3baf3aa37060476493f193- MD5
a3cd0b26426ee7da55b7591136822b29
About this file
ps4-emulator-update-apkod.apk is an Android file of 103.1 kB.
- Type and size
- Android · 103.1 kB
- Signer
- Not applicable
- First seen
- Sep 20, 2022On VirusTotal.
- Submitted by
- 168 distinct sources
First scanned
Antivirus consensus
4 of 67 engines flagged this file
8 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-118 engines1flagged
- Tier-237 engines3flagged
- Low-trust12 engines0flagged
View all 75 engine results
- BitDefenderFalxMalicious: Android.Riskware.Nitol.B
- GoogleMalicious: Detected
- IkarusMalicious: Trojan.AndroidOS.Agent
- SymantecMobileInsightMalicious: AppRisk:Generisk
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudNo result
- ALYacClean
- Antiy-AVLClean
- APEXNo result
- ArcabitClean
- AvastClean
- Avast-MobileClean
- AVGClean
- AviraClean
- BitDefenderClean
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceNo result
- CynetClean
- DeepInstinctNo result
- DrWebClean
- ElasticNo result
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GridinsoftClean
- huorongClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoNo result
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- 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
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Chapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is ps4-emulator-update-apkod.apk safe, or is it malware?
What is ps4-emulator-update-apkod.apk?
How many antivirus engines detected ps4-emulator-update-apkod.apk?
What should I do if I already installed ps4-emulator-update-apkod.apk?
What is the SHA-256 hash of ps4-emulator-update-apkod.apk?
How up to date is this analysis of ps4-emulator-update-apkod.apk?
Community
Member reviews and reports for this exact file hash.