File scan report
Verdict Suspicious
Is dn Spy. dll safe? Treat it as suspicious.
No antivirus engine detected malware and evidence from the test run lacks harmful artifacts, but the corroborated open-upload sample-feed entry prevents a clean verdict.
Read the whole reasonShow less
Why Suspicious? A reference database lists it as malicious; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
If it came from a link, an attachment or a stranger, delete it.
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 run 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 it. If you need the program, download it again from the publisher's own website.
If you already ran 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 forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (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
0 of 71 flagged
- Flagged 0
- No detection 71
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 5y ago
Chapter 02
Why we think so
2 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
None of the 71 antivirus engines that checked it flagged the sample, including the major engines, and observed execution produced no malicious sandbox finding or named injection target. However, the unsigned file appears in a corroborated open-upload sample feed, creating unresolved provenance concerns despite the strong benign indicators.
No engine among the 75 available engines flagged this file, while 18 major antivirus engines reported no detection. It is an established sample submitted by thousands of sources since 2020, which weighs against a newly distributed threat. The sandbox runs produced no malicious finding, and the process-injection and security-evasion mappings lacked the artifacts needed to show those actions occurred. The recorded network names were identified as analysis-environment background activity, and all 30 inspected hosts lacked known hostile reputation. Nevertheless, the file is unsigned and its hash appears in a corroborated open-upload sample feed, so its origin cannot be treated as fully established.
What We Detected
None of the 71 antivirus engines that checked it flagged the file, including 18 major antivirus engines. The only community YARA match identified debug-symbol information and was generic, not tied to a malware family. The sample has also been widely submitted since 2020.
Threat Behavior
The sandbox runs returned no malicious finding and recorded no named process-injection target. Mappings associated with process injection and security-evasion activity were not backed by corresponding artifacts. The listed domains were analysis-environment background contacts, while all 30 distinct inspected hosts had no known hostile reputation.
What To Do Now
The remaining concern is provenance: the executable is unsigned and the exact hash appears in a corroborated open-upload sample feed. Keep security software enabled and obtain the component from the official dnSpy release channel or compare its hash against a trusted distribution before using it.
Where this verdict could be wrong2 caveats
- The file is unsigned, so there is no verified publisher identity tying these bytes to the dnSpy project.
- The hash appears in an open-upload sample feed, although such feeds accept public submissions and do not establish maliciousness by themselves.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- None of the 71 antivirus engines that checked it flagged the file.
- Eighteen major antivirus engines reported no detection.
- Sandbox execution produced no malicious finding and recorded no named injection target.
- All 30 inspected contacted hosts lacked known malicious or suspicious reputation.
- The file has been submitted by 3,638 sources across 8,289 submissions since 2020.
- The executable has no verified publisher signature.
- The exact hash appears in a corroborated open-upload sample feed, which raises a provenance concern even though such listings are not malware confirmation.
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 6 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 6isolated sandbox runs
- 10sandbox rule tags
- 3spawned processes
- 20network contacts
- 28filesystem & 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: 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.
Note: Looked through folders on the test computer (most installers do this).
Note: Loaded extra code modules while running.
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 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.
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
dnSpy.dll
bc1c4e0fc49c138bbfc223d3e94231cd4884439c663646d91e48fa005df6704a
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
executable.exe
"C:\Users\<USER>\AppData\Local\Temp\executable.exe"
Test run - Evidence 3 of 7: ProcessSeen in the test run
bc1c4e0fc49c138bbfc223d3e94231cd4884439c663646d91e48fa005df6704a.exe
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
NGenTask.exe.log
C:\Users\user\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\NGenTask.exe.log
Test run - Evidence 5 of 7: Written fileSeen in the test run
ngen.log
C:\Users\user\AppData\Local\Microsoft\CLR_v4.0_32\ngen.log
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
13.107.39.203
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
209.197.3.8
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes the sandbox verdicts, 10 mapped techniques, every process, file, registry and network entry and 3 dropped files.
Show the technical evidenceChapter 04
Technical details
None of the 71 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.
File fingerprint
- Last analyzed
- Oct 18, 2026, 5:11 PM UTC
- SHA-256
bc1c4e0fc49c138bbfc223d3e94231cd4884439c663646d91e48fa005df6704a- SHA-1
edeaac9111d8f499378b67c983f7b7defbddb268- MD5
5cf180fec9628c4df4267de3ed7a98a7
About this file
dnSpy.dll is a Win32 EXE file of 212.0 kB.
- Claims to be
- dnSpyFrom the file's own version information, written by whoever built it.
- Original name
- dnSpy.dllMatches the shared file name.
- Type and size
- Win32 EXE · 212.0 kB
- Signer
- UnsignedNo code signature.
- First seen
- Dec 8, 2020On VirusTotal.
- Submitted by
- 3,638 distinct sources
- Packer
- None detected
- Entropy
- 4.51 of 8
First scanned Updated
Verdict history
- Malicious
- Suspiciousafter a new scan
Ratings change when antivirus engines, our checks or MalwareTips staff learn more about a file.
Includes every engine result (75), 3 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 6 questions people ask most about this file.
Is dnSpy.dll safe, or is it malware?
What is dnSpy.dll?
How many antivirus engines detected dnSpy.dll?
What should I do if I already ran dnSpy.dll?
What is the SHA-256 hash of dnSpy.dll?
How up to date is this analysis of dnSpy.dll?
Community
Member reviews and reports for this exact file hash.