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.
What this file did when executed
This file was detonated in 6 sandboxes and its runtime behaviour was observed.
Sandbox verdicts
1- VT: CLEANclean
Techniques observed in the sandbox
10MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1055· Process injection
- T1057· Lists programs
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1095· Custom network
- T1129· Loads modules
- T1497· Sandbox evasion
- T1518.001· Checks your AV
- T1562.001· Disables security
Observed activity
Processes started
3Programs the file ran, with their command lines.
executable.exe"C:\Users\<USER>\AppData\Local\Temp\executable.exe"bc1c4e0fc49c138bbfc223d3e94231cd4884439c663646d91e48fa005df6704a.exe%SAMPLEPATH%\bc1c4e0fc49c138bbfc223d3e94231cd4884439c663646d91e48fa005df6704a.exe3838354748.exe%SAMPLEPATH%\3838354748.exe
Network contacts
2020 hosts, listed as 20 addresses. Links show the host and path only.
- IP address
13.107.39.203 - IP address
209.197.3.8 - IP address
104.74.71.29 - IP address
52.184.215.140 - IP address
168.62.242.76 - IP address
23.216.147.179
Show all 20 entries for network contacts
- IP address
104.86.182.8 - IP address
104.112.185.183 - IP address
23.62.209.152 - IP address
23.209.116.25 - IP address
23.202.200.244 - IP address
184.29.167.249 - IP address
23.213.34.173 - IP address
23.213.34.147 - IP address
104.97.46.144 - IP address
23.44.253.134 - IP address
23.32.75.30 - IP address
23.219.78.81 - IP address
23.197.238.105 - IP address
23.204.150.28
Files
23Files the file created, changed or deleted.
- Written
C:\Users\user\AppData\Local\Microsoft\CLR_v4.0_32\UsageLogs\NGenTask.exe.log - Written
C:\Users\user\AppData\Local\Microsoft\CLR_v4.0_32\ngen.log - Written
\Device\ConDrv - Written
\Device\ConDrv\\Connect - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER116E.tmp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WER116E.tmp.txt
Show all 23 entries for files
- Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WEREBE.tmp - Written
C:\ProgramData\Microsoft\Windows\WER\Temp\WEREBE.tmp.csv - Deleted
C:\Windows\System32\spp\store\2.0\cache\cache.dat - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER6378.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER6433.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER6473.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER6CC0.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER6CD0.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER6CD1.tmp.txt - Deleted
C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\Microsoft\Crypto\Keys\de7cf8a7901d2ad13e5c67c29e5d1662_cbbb49d6-b7ff-44ca-aba5-8a5e250d4d42 - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F0C.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F1E.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WER1F1F.tmp.txt - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WEREB1B.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WEREB1C.tmp.WERInternalMetadata.xml - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WEREBF7.tmp.csv - Deleted
C:\ProgramData\Microsoft\Windows\WER\Temp\WEREC27.tmp.txt
Registry and auto-start
15Settings the file changed, including ways to start again after a restart.
- Set
HKLM\Software\Microsoft\WBEM\CIMOM\ConfigValueEssNeedsLoading - Set
HKLM\Software\Microsoft\WBEM\CIMOM\List of event-active namespaces - Set
HKLM\SYSTEM\ControlSet001\Control\DeviceClasses\{ad498944-762f-11d0-8dcb-00c04fc3358c}\##?#SW#{eeab7790-c514-11d1-b42b-00805fc1270e}#asyncmac#{ad498944-762f-11d0-8dcb-00c04fc3358c}\#{78032B7E-4968-42D3-9F37-287EA86C0AAA}\SymbolicLink - Set
HKLM\SYSTEM\ControlSet001\Control\DeviceClasses\{cac88484-7515-4c03-82e6-71a87abac361}\##?#SW#{eeab7790-c514-11d1-b42b-00805fc1270e}#asyncmac#{cac88484-7515-4c03-82e6-71a87abac361}\#\Control\Linked - Set
HKLM\SYSTEM\ControlSet001\Services\WmiApRpl\Performance\Last Counter - Set
HKLM\SYSTEM\ControlSet001\Services\WmiApRpl\Performance\Object List
Show all 15 entries for registry and auto-start
- Set
HKLM\SYSTEM\ControlSet001\Services\WmiApRpl\Performance\Last Help - Set
HKLM\SYSTEM\ControlSet001\Services\WmiApRpl\Performance\First Counter - Set
HKLM\SYSTEM\ControlSet001\Services\WmiApRpl\Performance\First Help - Set
HKLM\SYSTEM\ControlSet001\Services\WmiApRpl\Performance\PerfIniFile - Set
HKU\S-1-5-21-575823232-3065301323-1442773979-1000_CLASSES\Local Settings\MuiCache\17b\52C64B7E\LanguageList - Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\system32\drivers\ndis.sys[MofResourceName] - Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\System32\Drivers\portcls.SYS[PortclsMof] - Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\system32\drivers\en-US\ACPI.sys.mui[ACPIMOFResource] - Set
HKLM\Software\Microsoft\WBEM\WDM\%windir%\system32\DRIVERS\HDAudBus.sys[HDAudioMofName]
Mutexes
5Named locks a program uses so only one copy runs; malware families often reuse them.
DBWinMutex\Sessions\1\BaseNamedObjects\DBWinMutex\BaseNamedObjects\Local\SM0:4484:304:WilStaging_02\BaseNamedObjects\Local\SM0:2328:304:WilStaging_02\BaseNamedObjects\Local\SM0:6044:304:WilStaging_02
Sandbox background — not the file
27The analysis machine's own processes and connections, recorded in every run.
- VM process
wuapihost.exeC:\Windows\System32\wuapihost.exe - VM process
updater.exeC:\Program Files (x86)\Google3376_1875057168\bin\updater.exe - VM process
updater.exeC:\Program Files (x86)\Google3404_685209151\bin\updater.exe - VM process
UI0Detect.exeC:\Windows\System32\UI0Detect.exe - VM process
updater.exeC:\Program Files\Google3832_1568723803\bin\updater.exe - VM process
updater.exeC:\Program Files\Google2992_1340248737\bin\updater.exe
Show all 27 entries for sandbox background — not the file
- VM process
updater.exeC:\Program Files\Google480_1300451031\bin\updater.exe - VM process
updater.exeC:\Program Files\Google3756_701225760\bin\updater.exe - VM process
updater.exeC:\Program Files\Google3220_1221952147\bin\updater.exe - VM process
updater.exeC:\Program Files\Google3060_1209869807\bin\updater.exe - VM process
updater.exeC:\Program Files\Google1832_1393617651\bin\updater.exe - VM process
updater.exeC:\Program Files\Google2560_983303427\bin\updater.exe - VM injection target
\\?\C:\Windows\system32\wbem\WMIADAP.EXE - VM injection target
C:\Program Files (x86)\Google3376_1875057168\bin\updater.exe - VM injection target
C:\Program Files (x86)\Google3404_685209151\bin\updater.exe - VM injection target
C:\Program Files\Google3832_1568723803\bin\updater.exe - VM injection target
C:\Program Files\Google2992_1340248737\bin\updater.exe - VM host
query.prod.cms.rt.microsoft.com - VM host
www.microsoft.com - VM host
res.public.onecdn.static.microsoft - VM host
52.4.107.13.in-addr.arpa - VM host
245.50.188.52.in-addr.arpa - VM host
61.234.212.23.in-addr.arpa - VM host
16.152.214.23.in-addr.arpa - VM host
fp2e7a.wpc.phicdn.net - VM host
154.210.82.20.in-addr.arpa - VM host
fp2e7a.wpc.2be4.phicdn.net
Files this sample writes at runtime
This file drops 3 children at runtime. None are currently flagged malicious in our cache. 3 have no saved verdict and were not checked; that is missing coverage, not a finding.
- b322c48534c6fd3cc832…168519Not checkedno saved verdict
- cf43b3fb213b0444d2ff…ee939bNot checkedno saved verdict
- db4ee0c04efaba17bfa8…ad8b41Not checkedno saved verdict
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.
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.
Antivirus consensus
0 of 71 engines flagged this file
4 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-118 engines0flagged
- Tier-236 engines0flagged
- Low-trust17 engines0flagged
View all 75 engine results
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVClean
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleClean
- GridinsoftClean
- huorongClean
- IkarusClean
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureClean
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighClean
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrapmineClean
- TrellixENSClean
- TrendMicroClean
- TrendMicro-HouseCallClean
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexClean
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Community YARA rules matched, but all of them are generic capability, anti-debug or compiler rules that ordinary software also matches. Worth noting, not on their own cause for alarm.
- pdb_YARAifygeneric
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)The sample contacted an external IP address directly and no application domain was recorded. Direct-IP traffic also occurs in legitimate installers and infrastructure, so this is supporting context only and requires corroboration from host reputation and other runtime evidence.
Evidence209.197.3.8
Section entropy & packers
No high-entropy executable section or known packer signature was detected. Data and resource sections can still have high entropy without indicating packed code.
How widely this file has been seen
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Chapter 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.