File scan report
Verdict Malicious
Is version. dll safe? No, we rate this exact file malicious.
Unsigned 5.5 MB DLL with strong major consensus on crack/hacking tool family and four offensive MITRE techniques.
Read the whole reasonShow less
Strong evidence · Two or more major antivirus engines agree.
Delete the file and scan any systems that executed it; maintain current antivirus definitions.
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 use it unless you got it on purpose for security testing on systems you own. 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 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 used 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
33 of 69 flagged
- Flagged 33
- No detection 36
- No result 6
- Code signing Unsigned
- Test run Completed
- First seen 7y ago
Chapter 02
Why we think so
4 points against it and 0 in its favour, checked against the scan evidence.
The reasoning behind this verdict
33 of the 69 antivirus engines that checked it flag the file, including six major detections that converge on the crack family.
The combination of a strong major family consensus on crack, confirmed hacking tool labels, and four offensive MITRE techniques observed in sandbox outweighs the file's age and wide distribution. Lack of code signing and direct-IP contacts without domain resolution add further risk. No test-file or signed-commercial-FP patterns apply.
What We Detected
33 of the 69 antivirus engines that checked it report the sample malicious; six major antivirus engines agree on the crack family.
Threat Behavior
Sandbox execution shows direct-IP connections, rundll32 side-loading patterns, and multiple crash-dump artifacts consistent with loader activity. Ten files it created were dropped, none of which have independent malicious verdicts yet.
What To Do Now
Do not execute or distribute the file. Keep security software enabled and remove the sample from any systems where it was introduced.
Where this verdict could be wrong1 caveat
- One community comment claims two years of use with no issues, but this is anecdotal and outweighed by the major consensus.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Strong major consensus on crack/hacking tool family
- Unsigned DLL with offensive MITRE techniques
- Direct-IP control-server traffic observed
- Common filename (version.dll) used for sideloading
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- 29sandbox rule tags
- 9spawned processes
- 4network contacts
- 40filesystem & 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: Unpacked hidden content while it ran.
Moderate concern: Checked whether it was running on a test computer.
Moderate concern: Hid files or windows on the test computer.
Note: Read the network settings of the test computer.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as creating a scheduled task; none was recorded.
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 creating a service; no new service 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
version.dll
4e12ff9a72b7c2357f46ef645400cb6311330ced73ee787244c85ba7c57e8c8e
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
rundll32.exe
"C:\Windows\System32\rundll32.exe" "C:\Users\<USER>\Desktop\library.dll",#1
Test run - Evidence 3 of 7: ProcessSeen in the test run
loaddll32.exe
C:\Windows\System32\loaddll32.exe loaddll32.exe "C:\Users\user\Desktop\readme.dll"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
AppCrash_loaddll32.exe_8e2b68384082682205c3ef7e225c68e5e4a4e_f2262bc1_162cfb15
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_loaddll32.exe_8e2b68384082682205c3ef7e225c68e5e4a4e_f2262bc1_162cfb15
Test run - Evidence 5 of 7: Written fileSeen in the test run
Report.wer
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_loaddll32.exe_8e2b68384082682205c3ef7e225c68e5e4a4e_f2262bc1_162cfb15\Report.wer
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
52.147.198.201
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
34.120.208.123
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes 29 mapped techniques, every process, file, registry and network entry and 10 dropped files.
Show the technical evidenceChapter 04
Technical details
33 of the 69 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 33
- ESET-NOD32 (major engine)Win32/HackTool.Crack.NJ potentially unsafe application
- Fortinet (major engine)Riskware/Crack
- GData (major engine)Win32.Trojan.Agent.AUG9UD
- Microsoft (major engine)HackTool:Win32/Crack!MTB
- Sophos (major engine)Generic Reputation PUA (PUA)
- TrellixENS (major engine)GenericRXUO-NK!CC165AF6A6E4
- TrendMicro (major engine)HackTool.Win32.Crack.D
- TrendMicro-HouseCall (major engine)HackTool.Win32.Crack.D
File fingerprint
- Last analyzed
- Aug 24, 2026, 12:14 PM UTC
- SHA-256
4e12ff9a72b7c2357f46ef645400cb6311330ced73ee787244c85ba7c57e8c8e- SHA-1
3767e079d784c5a2b5088de7c172da1c1bf63daf- MD5
cc165af6a6e4978c66a86b25cf58b92b
About this file
version.dll is a Win32 DLL file of 5.6 MB.
- Type and size
- Win32 DLL · 5.6 MB
- Signer
- UnsignedNo code signature.
- First seen
- Sep 19, 2019On VirusTotal.
- Submitted by
- 3,712 distinct sources
- Packer
- None detected
- Entropy
- 7.96 of 8
First scanned
Includes every engine result (75), 1 matched signature rule, 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 version.dll a virus?
What is version.dll?
How many antivirus engines detected version.dll?
What should I do if I already used version.dll?
How do I remove version.dll?
What kind of program is version.dll?
What is the SHA-256 hash of version.dll?
How up to date is this analysis of version.dll?
Community
Member reviews and reports for this exact file hash.