File scan report
Verdict Malicious
Is unknown safe? No, we rate this exact file malicious.
This unsigned, VMProtect-protected 64-bit DLL is flagged by 43 of the 69 antivirus engines that checked it, including eleven independent major antivirus engines, though they name…
Read the whole reasonShow less
Strong evidence · Two or more major antivirus engines agree.
Delete this DLL and the package it came with, then run a full scan with your security software kept enabled.
What to do now4 steps
This file is harmful. Don't run it, and remove it.
If you haven't used it
Don't use this component. Let your antivirus remove this component, then repair or reinstall the program it belongs to from its official website. Don't delete or replace the file by hand.
If you already used it
Disconnect the device from the internet, then run a full antivirus scan. Microsoft Defender Offline (Windows Security > Virus & threat protection > Scan options) also finds malware that hides while Windows runs.
If you typed passwords on the device after running it, change them from another device you trust.
If the scan keeps finding it, or the device still acts strangely, scan again with a second-opinion scanner from another company; if that doesn't fix it, back up your personal files and reinstall Windows.
If you already ran it, do these in order.
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.
Antivirus results
43 of 69 flagged
- Flagged 43
- No detection 26
- No result 6
- Code signing Unsigned
- Test run Completed
- First seen 1y ago
Chapter 02
Why we think so
4 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
43 of the 69 antivirus engines that checked it flag this DLL, including Microsoft, Symantec, TrendMicro, BitDefender and Avira. The file is unsigned and heavily protected with VMProtect, which hides its code. The sandbox runs showed no overtly hostile actions. Some labels point to crack or riskware tooling, but the weight of major detections makes it unsafe to run.
Detection coverage is strong. 43 of the 69 antivirus engines that checked it flag the file, with 32 independent detection votes and 11 of them from major antivirus engines. Every label is a generic trojan bucket or a packer, riskware or crack label, so no specific family can be named. The DLL is unsigned and wrapped in VMProtect, so its real code is encrypted and hard to inspect. In three sandbox runs it was loaded through rundll32, and none returned a malicious verdict. No injection or persistence was recorded, and every contacted host was a Microsoft or MSN service with no malicious reputation. Even so, broad major agreement on an unsigned, protected library is a strong reason to treat it as harmful.
What We Detected
43 of the 69 antivirus engines that checked it flag this 64-bit Windows DLL. They include eleven independent major antivirus engines such as Microsoft, Symantec, TrendMicro, BitDefender, Avira, Avast and Sophos. The labels are generic trojan detections; a few engines describe it as riskware or crack-related software. The file is unsigned and protected with VMProtect, which encrypts most of its code.
Threat Behavior
Three sandbox runs loaded the library. They recorded no injection into other processes, no persistence and no malicious sandbox verdict. The network contacts were Microsoft and MSN services with no malicious reputation. The heavy code protection means hostile logic may stay hidden until specific conditions are met.
What To Do Now
Do not load or run this DLL. If it arrived with a game mod, cheat or crack, remove that package. Run a full scan with your security software and keep it enabled.
Where this verdict could be wrong3 caveats
- Several detections are unwanted program, riskware or crack labels. The file may be a protected game cheat or crack library rather than a classic trojan.
- The sandbox runs recorded no injection, no persistence and no malicious verdict. The observed network contacts were Microsoft and MSN hosts with no malicious reputation.
- More than 1,300 distinct submitters over 450 days show the file is widely circulated.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- The sandbox runs recorded no injection, persistence or malicious verdict
- None of the contacted hosts has a malicious or suspicious reputation
- Widely seen, with more than 1,300 distinct submitters over 450 days
- Flagged by 43 of the 69 antivirus engines that checked it, including eleven independent major antivirus engines
- Unsigned DLL with no publisher identity
- Heavily protected with VMProtect, which hides its code
- Some engines label it as crack or riskware software
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 3 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 3isolated sandbox runs
- 9sandbox rule tags
- 8spawned processes
- 5network contacts
- 7filesystem & 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: Checked whether it was running on a 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.
Note: Checked which security software was installed on the test computer.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as setting up auto-start; no auto-start entry 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 cracked-software installers work
A crack or patch installer is one of the most common ways to spread trojans. Even if the program seems to work, it can install malware in the background.
Bottom line:There is no safe copy of a cracked installer: delete it, and get the software from its real publisher.
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
unknown
f9ebce21fdf5695eaa9e8c2891b5781dd54cf177cdc102e0d2858269c793683e
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
rundll32.exe
"C:\Windows\sysnative\rundll32.exe" "C:\Users\<USER>\Desktop\discord_game_sdk.dll",#1
Test run - Evidence 3 of 7: ProcessSeen in the test run
loaddll64.exe
C:\Windows\System32\loaddll64.exe loaddll64.exe "C:\Users\user\Desktop\discord_game_sdk.dll"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
Logs
C:\ProgramData\Microsoft\Windows Security Health\Logs
Test run - Evidence 5 of 7: Written fileSeen in the test run
Connect
\Device\ConDrv\\Connect
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
config-edge-skype.ln-0007.ln-msedge.net
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
ln-0007.ln-msedge.net
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes 9 mapped techniques and every process, file, registry and network entry.
Show the technical evidenceChapter 04
Technical details
43 of the 69 antivirus engines that checked it flag it; no publisher signature.
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 43
- Avast (major engine)Win64:MalwareX-gen [Trj]
- AVG (major engine)Win64:MalwareX-gen [Trj]
- Avira (major engine)TR/W64.MalwareX
- BitDefender (major engine)Trojan.GenericKD.77181856
- Emsisoft (major engine)Trojan.GenericKD.77181856 (B)
- ESET-NOD32 (major engine)Win64/Packed.VMProtect.AC suspicious application
- F-Secure (major engine)Trojan.TR/W64.MalwareX
- Fortinet (major engine)Riskware/Application
File fingerprint
- Last analyzed
- Oct 22, 2026, 3:37 PM UTC
- SHA-256
f9ebce21fdf5695eaa9e8c2891b5781dd54cf177cdc102e0d2858269c793683e- SHA-1
b636ac5d21e3be875479afcf08da8f14e0a5f123- MD5
e880ce6b5f85abf90ae8240c9e09a3d4
About this file
unknown is a Win32 DLL file of 14.6 MB.
- Type and size
- Win32 DLL · 14.6 MB
- Signer
- UnsignedNo code signature.
- First seen
- Jul 29, 2025On VirusTotal.
- Submitted by
- 1,329 distinct sources
- Packer
- VMProtect 2.XX-3.XX (DetectItEasy protector)Packing hides code; legitimate installers use it too.
- Entropy
- 7.85 of 8A code section is highly compressed or encrypted.
First scanned
Includes every engine result (75), 2 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 unknown a virus?
What is unknown?
How many antivirus engines detected unknown?
What should I do if I already used unknown?
How do I remove unknown?
What kind of malware is unknown?
What is the SHA-256 hash of unknown?
How up to date is this analysis of unknown?
Community
Member reviews and reports for this exact file hash.