Is dotnet-wave-bootstrapper.dll safe?
No antivirus engine detected this widely submitted file, and its completed sandbox run produced no malicious verdict, persistence, or dropped payloads.
All 75 antivirus engines were free of detections, including 17 tier-1 engines, while one completed sandbox run produced no malicious verdict. The unsigned status, defense-evasion technique, and direct-IP contact warrant normal caution, especially because the contacted address did not receive a complete reputation check.
837d1b77abef74e3fc…ed03b6a0cbc602Recommended next actions
Before using
Use it only as part of software obtained from the developer's official site or another source you independently trust.
If you already used it
Keep normal device protection enabled and stop if the file behaves unexpectedly.
Intelligence
The saved assessment, checked against the scan evidence and recorded coverage.
The reasoning behind this verdict
This section explains the evidence supporting the verdict and keeps conflicting or missing signals visible.
All 75 antivirus engines were free of detections, including 17 tier-1 engines, while one completed sandbox run produced no malicious verdict. The unsigned status, defense-evasion technique, and direct-IP contact warrant normal caution, especially because the contacted address did not receive a complete reputation check.
The strongest evidence is the complete absence of detections across 75 antivirus engines, including all 17 tier-1 engines. One completed sandbox run produced no malicious verdict, persistence indicators, or dropped-file hashes. Broad circulation across 840 sources and 984 submissions also reduces the likelihood of a narrowly distributed threat. Static analysis found neither high-entropy code nor likely packing, and three external-intelligence checks supplied no corroborating hit. Counter-signals are the missing signature, observed T1562.001 activity, and a direct-IP connection whose reputation was not fully checked, but these do not outweigh the broader evidence.
What We Detected
No detections were reported across 75 antivirus engines, including 17 tier-1 engines. The sample is unsigned, but it has circulated broadly, with 840 sources accounting for 984 submissions. Static PE analysis found no likely packing or high-entropy code, while CIRCL, MalwareBazaar, and YARAify supplied no matching intelligence.
Threat Behavior
One completed sandbox run produced no malicious verdict, persistence indicators, or dropped-file hashes. It did record T1562.001 and a connection to 162.159.36.2. Because the contacted-host reputation check was not completed or saved, that address cannot be characterized as benign or malicious from this evidence.
What To Do Now
Keep endpoint protection enabled and obtain the file from its official distribution channel where possible. If its source is unexpected or untrusted, verify the SHA-256 value and monitor execution rather than granting elevated privileges automatically.
Where this verdict could be wrong4 caveats
- signing.signed=false, so no authenticated publisher identity supports the file.
- T1562.001 was observed and MalwareTips.Synth.DirectIpC2 fired for 162.159.36.2; contactedHosts=null leaves that IP without a completed reputation cross-check.
- similarHashes shows 2/2 prior 'safe' verdicts for matchKind=imphash, but signerMatchesSubject=false in both cases makes these weak framework-level similarities.
- communityComments[0].tags includes 'exeinfection', but the annotation provides no corroborated family detection or engine finding.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/75 antivirus engines reported a malicious or suspicious result.
- All 17 tier-1 engines reported no detection.
- One completed sandbox run had no malicious verdict, persistence, or dropped hashes.
- The file appeared across 840 sources and 984 submissions.
- No packer, high-entropy code, MalwareBazaar hit, CIRCL hit, or YARAify rule was found.
- The executable is unsigned and has no established signer history.
- Runtime observation included MITRE technique T1562.001.
- The sample contacted 162.159.36.2 directly, and no complete host-reputation result is available.
- A community annotation applied the tag 'exeinfection' without independent detection corroboration.
Keep security software enabled and prefer a copy obtained from the software's official source. Exercise additional caution if the file arrived unexpectedly or requests administrator privileges.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete1 signature or behavior rule matched.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 9MITRE ATT&CK techniques
- 1spawned processes
- 1network contacts
- 3filesystem & mutex artifacts
What this file did when executed
This file was detonated in 1 sandbox and its runtime behaviour was observed.
Adversary techniques mapped to the MITRE ATT&CK framework.
- 162.159.36.2
- C:\ProgramData\Microsoft\NetFramework\BreadcrumbStore\netcore,Microsoft.WindowsDesktop.App.Runtime.win-x64
- C:\ProgramData\Microsoft\NetFramework\BreadcrumbStore\netcore,Microsoft.WindowsDesktop.App.Runtime.win-x64,9.0.2
- C:\ProgramData\Microsoft\NetFramework\BreadcrumbStore\netcore,Newtonsoft.Json,13.0.4
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 1rule hit recorded
- 0 / 75engines flagged
- 840sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 984 times from 840 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: dotnet-wave-bootstrapper.dll — 837d1b77abef74e3fc4f1c717a9077daf06f91255be613c9dced03b6a0cbc602
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\user\Desktop\dotnet-wave-bootstrapper.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
File written: netcore,Microsoft.WindowsDesktop.App.Runtime.win-x64 — C:\ProgramData\Microsoft\NetFramework\BreadcrumbStore\netcore,Microsoft.WindowsDesktop.App.Runtime.win-x64
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: netcore,Microsoft.WindowsDesktop.App.Runtime.win-x64,9.0.2 — C:\ProgramData\Microsoft\NetFramework\BreadcrumbStore\netcore,Microsoft.WindowsDesktop.App.Runtime.win-x64,9.0.2
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
Contacted host: 162.159.36.2 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
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.
Evidence162.159.36.2
0 of 75 engines flagged this file
View all 75 engine results
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
Lots of people are uploading this but it's recent — typical of newly-released legitimate software. Low prior for malware.
Fingerprint and provenance
- File name
- dotnet-wave-bootstrapper.dll
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 8.2 MB
- Last analyzed
- Sep 30, 2026, 8:06 PM UTC
837d1b77abef74e3fc4f1c717a9077daf06f91255be613c9dced03b6a0cbc602Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file appears low risk based on the evidence available now.
- Recovery step 01
Use it only as part of software obtained from the developer's official site or another source you independently trust.
- Recovery step 02
A clean result reduces known risk, but it cannot guarantee that every new or targeted threat has been detected.
- Recovery step 03
Keep your antivirus and Windows updates switched on so you stay protected.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is dotnet-wave-bootstrapper.dll safe?
What is dotnet-wave-bootstrapper.dll?
How many antivirus engines detected dotnet-wave-bootstrapper.dll?
What is the SHA-256 hash of dotnet-wave-bootstrapper.dll?
Is it safe to use dotnet-wave-bootstrapper.dll?
How up to date is this analysis of dotnet-wave-bootstrapper.dll?
Community
Member reviews and reports for this exact file hash.