Is rayburst.exe safe?
Only 1 of 75 engines flagged this unsigned executable, using a generic low-trust machine-learning label, while all 17 reporting tier-1 engines found nothing.
The sole detection comes from Trapmine and uses a generic machine-learning label; no tier-1 engine or independent intelligence source corroborates it. This strongly suggests a false positive, although the unsigned file is newly observed and lacks completed runtime analysis, so it should still be obtained from a trustworthy source.
14815610854681d0da…9eeb47b06b284dRecommended next actions
Before running
Run it only when it came from the developer's official site or another source you independently trust.
If you already ran 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.
The sole detection comes from Trapmine and uses a generic machine-learning label; no tier-1 engine or independent intelligence source corroborates it. This strongly suggests a false positive, although the unsigned file is newly observed and lacks completed runtime analysis, so it should still be obtained from a trustworthy source.
Only 1 of 75 engines flagged the sample, and that result came from a low-trust detector using a generic machine-learning label rather than a named malware family. All 17 reporting tier-1 engines, including Kaspersky, BitDefender, ESET-NOD32, Avast, and Fortinet, reported no detection. No supporting YARA rules, known malware-feed match, suspicious packing, or fired heuristic was found. The executable is unsigned and has appeared in only one submission, which limits publisher assurance and reputation evidence. No completed sandbox observation or comprehensive contacted-host reputation result is available, so the assessment rests primarily on static scanning evidence.
What We Detected
Trapmine was the only engine to flag the file, producing a generic machine-learning label. That represents 1 of 75 engines, with zero tier-1 detections and no agreement on a malware family. All 17 reporting tier-1 engines found no detection.
Threat Behavior
No completed sandbox observation is available, so runtime behavior cannot be characterized. The file was not identified as packed, its code section was not marked high-entropy, no static heuristic fired, and no YARA or known malware-feed match corroborated the lone detection. A complete reputation check of any contacted hosts was not available.
What To Do Now
Confirm that the file came from the developer's official release channel and compare its SHA-256 value, 14815610854681d0da7e938d0bda001fce5f97d7ce577273179eeb47b06b284d, with a publisher-provided checksum if one exists. Keep endpoint protection enabled, and avoid running the file if its origin is uncertain or its behavior differs from what was expected.
Where this verdict could be wrong3 caveats
- signing.signed=false: rayburst.exe is an unauthenticated Windows executable, so its publisher and integrity cannot be verified.
- prevalence.classification=rare_new: the sample is recently observed and has only one recorded submission.
- behaviour=null and contactedHosts=null leave runtime activity and contacted-host reputation untested.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only 1/75 engines detected the sample
- engines.tier1Malicious=0 and engines.onlyLowTrustFlagging=true
- All 17 reporting tier-1 engines found no detection
- No YARAify or MalwareBazaar corroboration
- peAnalysis.likelyPacked=false and peAnalysis.highEntropyCode=false
- Unsigned Windows executable with no verifiable publisher identity
- Recently observed sample with only one recorded submission
- No completed runtime observation
- No complete contacted-host reputation result
Use the file only if it came directly from a trusted developer or official release channel, and verify its SHA-256 checksum where possible. Keep endpoint protection enabled and seek runtime analysis if the source cannot be confirmed.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 of 75 engines flagged the file.
Sandbox
PartialRuntime data is present, but no completed sandbox environment is recorded.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
CompleteRule evaluation completed with no recorded matches.
External intel
Complete3 of 3 independent reference sources completed.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime behavior was not available
The report does not treat a missing runtime observation as a clean result.
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 0rule hits recorded
- 1 / 75engines flagged
- 1sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
No completed runtime observation is available for this file.
ProvenanceDerivedSourceRuntime coverageObserved at - 02
1 of 75 antivirus engines flagged the file, including Trapmine.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved 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.
YARA rules
No matchesThe rule pass completed without a saved public match.
1 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
Barely seen in the wild and first surfaced recently. 1 antivirus detection make that low prevalence materially relevant, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- rayburst.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 34.8 MB
- Last analyzed
- Oct 5, 2026, 6:34 PM UTC
14815610854681d0da7e938d0bda001fce5f97d7ce577273179eeb47b06b284dSafety & 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
Run it only when it came 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 rayburst.exe safe?
What is rayburst.exe?
How many antivirus engines detected rayburst.exe?
What is the SHA-256 hash of rayburst.exe?
Is it safe to run rayburst.exe?
How up to date is this analysis of rayburst.exe?
Community
Member reviews and reports for this exact file hash.