File scan report

Verdict Suspicious

Analyzed , 8 days ago

Is dnSpy.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.

Don't run it until you know where it came from

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

  1. Don't run it unless you're sure where it came from.

  2. Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.

  3. 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

  1. 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.

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
FilednSpy.dll212.0 kBSHA-256 bc1c4e0fc49c…f6704a
  • Code signing Unsigned
  • Test run Completed
  • First seen 5y ago
None of the 71 antivirus engines that checked it flag it.

Chapter 02

Why we think so

2 points against it and 5 in its favour, checked against the scan evidence.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

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.

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.

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.

Seen in the test runWorked out from other results
  1. Input file

    The submitted object

    1
    1. Evidence 1 of 7: FileSeen in the test run

      dnSpy.dll

      bc1c4e0fc49c138bbfc223d3e94231cd4884439c663646d91e48fa005df6704a

      Uploaded file
  2. Processes

    What ran

    2
    1. Evidence 2 of 7: ProcessSeen in the test run

      executable.exe

      "C:\Users\<USER>\AppData\Local\Temp\executable.exe"

      Test run
    2. Evidence 3 of 7: ProcessSeen in the test run

      bc1c4e0fc49c138bbfc223d3e94231cd4884439c663646d91e48fa005df6704a.exe

      Test run
    3. +1 more recorded observation
  3. Files

    Created or changed

    2
    1. 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
    2. 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
    3. +1 more recorded observation
  4. Network

    Hosts contacted

    2
    1. Evidence 6 of 7: Contacted hostSeen in the test run

      13.107.39.203

      Contacted during the test run.

      Test run
    2. Evidence 7 of 7: Contacted hostSeen in the test run

      209.197.3.8

      Contacted during the test run.

      Test run
    3. +1 more recorded observation

7 facts from the test run. See the full activity list.

Chapter 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.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 75 enginesCompletePositive signal: 0 of 71 engines flagged it · 4 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxes · C2AE, CAPA, CAPE SandboxComplete6 runs: 1 clean, 5 without a verdict Details for sandbox run
Contacted hostsMalwareTips URL scannerComplete30 contacted hosts checked Details for contacted hosts
Signature rulesYARAify community rules + MalwareTips rulesComplete1 community YARA rule (generic only) · 2 MalwareTips behaviour rules Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteWorth noting: Listed in an open-upload malware feed

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

  1. Malicious
  2. Suspiciousafter a new scan

Ratings change when antivirus engines, our checks or MalwareTips staff learn more about a file.

Chapter 05

Questions & answers

Short answers to the 6 questions people ask most about this file.

Is dnSpy.dll safe, or is it malware?
dnSpy.dll is rated Suspicious: some signs point to a problem, but nothing confirms it is harmful. No antivirus engine flags it; the caution comes from other evidence, such as who made it, how widely it is used or what it did in a test run. Don't run it unless you're sure where it came from. If you need the program, download it again from the publisher's own website.
What is dnSpy.dll?
dnSpy.dll is a Windows program, about 212.0 kB. Its version information says it is “dnSpy”. Version information is written by whoever built the file, so it is a claim, not proof of who made it. VirusTotal first saw it on Dec 8, 2020.
How many antivirus engines detected dnSpy.dll?
None of the 71 antivirus engines that checked it flag dnSpy.dll. A clean antivirus result is not proof of safety; the caution comes from other evidence, such as who made it, how widely it is used or what it did in a test run.
What should I do if I already ran dnSpy.dll?
No infection is confirmed: the rating is a caution, not a malware finding. 1) Check where it came from. If you can't confirm the source, delete it. 2) Run a full scan with your security software. 3) If the scan finds something, follow its removal steps and change passwords you typed on the device since then.
What is the SHA-256 hash of dnSpy.dll?
The SHA-256 fingerprint of dnSpy.dll is bc1c4e0fc49c138bbfc223d3e94231cd4884439c663646d91e48fa005df6704a, and its MD5 is 5cf180fec9628c4df4267de3ed7a98a7. Two files with the same SHA-256 are identical, so use it to check you have exactly this file, not just one with the same name.
How up to date is this analysis of dnSpy.dll?
This report reflects the scan on Oct 18, 2026. A file's fingerprint never changes, but antivirus engines keep learning, so a rating can change later. To get a newer result, scan the file again: we refresh the antivirus results when the saved ones are out of date.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Recent reports on other files with the same rating.

All file reports
This report and its SHA-256 fingerprint are public, so the next person who checks the same file gets an instant answer; documents and images are listed by type instead of their file name. A file we had not seen before is uploaded to VirusTotal, whose security partners and subscribers can download it; MalwareTips deletes its own copy after the scan. If you ran this file and are worried, scan your device with up-to-date security software.