File scan report
Verdict Malicious
Is emuext. exe safe? No, we rate this exact file malicious.
Unsigned 2.5 MB PE with six major hacking tool detections and evidence from the test run mapped to process-injection behavior.
Read the whole reasonShow less
Strong evidence · Two or more major antivirus engines agree.
Delete the file and scan the system with up-to-date security software; do not run or distribute crack tools.
What to do now4 steps
This is a hacking tool. It is risky to keep and run, but finding it is not by itself a sign that the device is infected.
What to do
Don't run it unless you got it on purpose for security testing on systems you own. Delete it, then empty the Recycle Bin.
If you didn't put it on the device yourself, delete it and run a full antivirus scan: something else may have brought it.
Tools like this often come with cracked or pirated software. If it came that way, treat the whole download as unsafe and scan everything it installed.
If you already ran it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
If you opened or installed it
Avoid banking and sign-ins on that device until it is clean. These free MalwareTips guides walk you through it.
- Trojan removal guideClear steps for Windows, Mac and Android. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
37 of 54 flagged
- Flagged 37
- No detection 17
- No result 21
- Code signing Unsigned
- Test run Completed
- First seen 9y ago
Chapter 02
Why we think so
3 points against it and 0 in its favour, checked against the scan evidence.
The reasoning behind this verdict
37 of the 54 antivirus engines that checked it flag the file, six of them major, all converging on crack/hacking tool labels.
The combination of major hacking tool consensus, confirmed offensive MITRE techniques, and YARA hits on a packed loader outweigh the file's age and common distribution. Lack of code signing removes any benign-publisher benefit. No test-file or signed-installer exceptions apply.
What We Detected
37 of the 54 antivirus engines that checked it report the sample malicious; six major antivirus engines label it a crack or hacktool. YARAify matched four rules, including MALWARE_Win_Unknown_PackedLoader_01 and VMProtectStub. The binary is unsigned.
Threat Behavior
The sample wrote temporary DLLs and contacted 19 raw IP addresses without domain names.
What To Do Now
Do not execute the file. Keep security software enabled and remove the sample from disk.
- Unsigned executable
- Defense-evasion techniques
- Multiple major hacking tool detections
6 sources checked · 5 complete · 1 partial. See every source
Chapter 03
What it did in our test
It ran in our isolated test environment; no test environment rated what it did as risky.
Test run summary
Capture complete- 22sandbox rule tags
- 3spawned processes
- 3network contacts
- 38filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
Moderate concern: Ran commands or a script on the test computer.
Moderate concern: Used an unusual way to talk to a server.
Moderate concern: Checked whether it was running on a test computer.
Note: Listed the programs running on the test computer.
Note: Talked to servers over the internet during the test run.
Note: Read basic details of the test computer, such as its Windows version.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
Not confirmed: A sandbox rule tagged this run as recording keystrokes; no keylogging was confirmed.
Not confirmed: A sandbox rule tagged this run as weakening security settings; no setting change was recorded.
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.
Threat context
How hacking tools are used
Hacking tools are programs that can switch off security software, test passwords or attack other computers. Security professionals use them on purpose; criminals also bundle them with malware.
Bottom line:Keep it only if you installed it on purpose, and check how it got onto the device if you didn't.
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 7: FileSeen in the test run
emuext.exe
c2f6d462a20f92b97c49c3af19872fc4df6aabd4f66f4b8b298a1303881422f6
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
emuext.exe
Test run - Evidence 3 of 7: ProcessSeen in the test run
c2f6d462a20f92b97c49c3af19872fc4df6aabd4f66f4b8b298a1303881422f6.exe
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
spc_player.dll
C:\Documents and Settings\Administrator\Local Settings\Temp\spc_player.dll
Test run - Evidence 5 of 7: Written fileSeen in the test run
spc_player.dll
C:\Users\<USER>\AppData\Local\Temp\spc_player.dll
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
209.197.3.8
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
13.107.39.203
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes 22 mapped techniques, every process, file, registry and network entry and 2 dropped files.
Show the technical evidenceChapter 04
Technical details
37 of the 54 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 37
- ESET-NOD32 (major engine)Win32/HackTool.Crack.FS potentially unsafe application
- Fortinet (major engine)Riskware/Crack.FS
- GData (major engine)Application.Hacktool.YM
- Microsoft (major engine)HackTool:Win32/Agent
- Symantec (major engine)Trojan Horse
- TrendMicro (major engine)PUA.Win32.AdoPatch.A
- TrendMicro-HouseCall (major engine)PUA.Win32.AdoPatch.A
- AhnLab-V3Unwanted/Win32.KeyGen.R268822
File fingerprint
- Last analyzed
- Aug 24, 2026, 11:36 PM UTC
- SHA-256
c2f6d462a20f92b97c49c3af19872fc4df6aabd4f66f4b8b298a1303881422f6- SHA-1
16cccef91ee368f9e4bbf09c5eab30865b380150- MD5
a209b88b9b2cf7339be0ac5126417875
About this file
emuext.exe is a Win32 EXE file of 2.5 MB.
- Type and size
- Win32 EXE · 2.5 MB
- Signer
- UnsignedNo code signature.
- First seen
- Oct 31, 2016On VirusTotal.
- Submitted by
- 3,280 distinct sources
- Packer
- None detected
- Entropy
- 7.19 of 8
First scanned
Includes every engine result (75), 5 matched signature rules, PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 8 questions people ask most about this file.
Is emuext.exe a virus?
What is emuext.exe?
How many antivirus engines detected emuext.exe?
What should I do if I already ran emuext.exe?
How do I remove emuext.exe?
What kind of program is emuext.exe?
What is the SHA-256 hash of emuext.exe?
How up to date is this analysis of emuext.exe?
Community
Member reviews and reports for this exact file hash.