File scan report
Verdict Safe
Is Burst.
None of the 71 antivirus engines that checked it flagged this long-known executable, while static analysis and one completed sandbox run found no corroborating malware indicators.
Read the whole reasonShow less
Moderate evidence · No engine flags it, but no publisher signature confirms who made it.
Good practice2 tips
We found nothing harmful in this file.
Run it only if it came from the developer's own website or an official app store.
Keep your antivirus and Windows updates switched on.
No scanner can promise a file is 100% safe.
Antivirus results
0 of 71 flagged
- Flagged 0
- No detection 71
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 17y ago
Chapter 02
Why we think so
3 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
One completed sandbox run produced no malicious verdict or offensive-technique mapping, and the antivirus analysis found no packing indicators; however, the file is unsigned and no complete host-reputation check is available.
The strongest evidence is the complete absence of detections among 75 engines, with all 18 represented major antivirus engines remaining silent. The file has also been known since 2009, giving detection systems substantial time to identify it if it matched established malware. One completed sandbox run produced no malicious verdict, offensive-technique mapping, persistence indicator, or observed sample network contact. Static PE analysis found neither packing nor unusually high-entropy code and identified a conventional Microsoft Visual C++ toolchain. Assurance is reduced slightly because the executable is unsigned and the independent host-reputation cross-check was not completed.
What We Detected
None of the 71 antivirus engines that checked it flagged Burst.EXE, including all 18 represented major antivirus engines. The sample has been known since 2009, and no malware family label, researcher-specific YARA match, brand mismatch, or triggered rule was present.
Threat Behavior
One completed sandbox run produced no malicious verdict and mapped no offensive or MITRE techniques common in legitimate software. It recorded Dr. Watson crash-reporting activity involving dwwin.exe and a diagnostic log, but no persistence indicators or sample network contacts. The antivirus analysis found no packer, likely-packing condition, or high-entropy code.
What To Do Now
The evidence supports ordinary use if the file came from an expected source. Because it is unsigned, retain normal security software and verify the download source or hash before running it on a sensitive system.
Where this verdict could be wrong3 caveats
- The executable is unsigned, so its publisher and integrity are not authenticated.
- The host-reputation cross-check was unavailable, limiting independent network assessment.
- The sandbox recorded interaction with dwwin.exe and creation of a Dr. Watson log, although no offensive technique or malicious sandbox verdict accompanied it.
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.
- All 18 represented major antivirus engines remained silent.
- The sample has been known since 2009 without acquiring detections.
- One completed sandbox run produced no malicious verdict or offensive-technique mapping.
- The antivirus analysis found no packing or high-entropy code.
- The executable is unsigned, so there is no authenticated publisher identity.
- No complete reputation cross-check was available for contacted hosts.
- The sandbox recorded crash-reporting interaction with dwwin.exe, though it was not accompanied by an offensive-technique mapping or malicious verdict.
6 sources checked · 5 complete · 1 not needed or not applicable. 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- 1spawned processes
- 0network contacts
- 2filesystem & mutex artifacts
Includes every process, file, registry and network entry.
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 · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
File fingerprint
- Last analyzed
- Oct 13, 2026, 1:49 AM UTC
- SHA-256
46479165faf3d0bea7e270cea28bfb675a919b9b2cdef85ce0b3afd671a35f5b- SHA-1
83bbd66aabec12218354f7c02a0745beacf77f2c- MD5
007dacd0e063915a257b853c4e86ea8c
About this file
Burst.EXE is a Win32 EXE file of 360.4 kB.
- Type and size
- Win32 EXE · 360.4 kB
- Signer
- UnsignedNo code signature.
- First seen
- Jul 21, 2009On VirusTotal.
- Submitted by
- 5 distinct sourcesRarely seen: few people have submitted this exact file.
- Packer
- None detected
- Entropy
- 5.13 of 8
First scanned
Includes every engine result (75), 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 Burst.EXE safe?
What is Burst.EXE?
How many antivirus engines detected Burst.EXE?
What is the SHA-256 hash of Burst.EXE?
Is it safe to run Burst.EXE?
How up to date is this analysis of Burst.EXE?
Community
Member reviews and reports for this exact file hash.