Is Ventoy2Disk.exe safe?
No antivirus engine detected this widely submitted executable, and its completed sandbox run produced neither malware-exclusive techniques nor a harmful runtime assessment.
All 75 antivirus engines returned no malicious or suspicious detection, including 17 tier-1 engines. The file is unsigned and made direct-IP contacts whose reputations were not checked, but its extensive prevalence, unpacked structure, and lack of malware-exclusive runtime techniques strongly support legitimate software.
aa194a077ff8b57db0…748eb13f86b951Recommended 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.
All 75 antivirus engines returned no malicious or suspicious detection, including 17 tier-1 engines. The file is unsigned and made direct-IP contacts whose reputations were not checked, but its extensive prevalence, unpacked structure, and lack of malware-exclusive runtime techniques strongly support legitimate software.
The sample received no malicious or suspicious detections from 75 antivirus engines, with all 17 tier-1 engines silent. It has also accumulated 10,937 submissions from 3,660 sources over 566 days, which strongly reduces the likelihood of an unidentified active threat. One completed sandbox run recorded 15 benign-common techniques, no malware-exclusive techniques, and no harmful sandbox assessment. A direct-IP heuristic is the main technical concern, but no complete host-reputation result is available, so those contacts cannot be characterized as either benign or harmful. The executable is unsigned and its five inspected child files remain unclassified, yet neither point outweighs the broad antivirus agreement and established prevalence.
What We Detected
No malicious or suspicious result appeared among 75 antivirus engines. All 17 tier-1 engines reported no detection, and no engine family consensus, hacktool label, packing indicator, or external research-rule match was present. The file has been submitted 10,937 times by 3,660 sources over 566 days, indicating broad and established circulation.
Threat Behavior
One completed sandbox run recorded 15 ambient techniques and no malware-exclusive techniques or harmful sandbox assessment. The sample contacted 13 external IP addresses without application domains, triggering the MalwareTips.Synth.DirectIpC2 heuristic. Because contactedHosts is unavailable, no complete reputation assessment exists for those addresses. Five child files were inspected without a known harmful result, but their individual classifications remain unknown.
What To Do Now
The unsigned status means publisher authenticity cannot be confirmed from a certificate. Obtain the executable from Ventoy's official release channel, verify its SHA-256 value against the publisher's release information when available, and keep endpoint protection enabled while running it.
Where this verdict could be wrong4 caveats
- signing.signed=false despite signing.applicable=true, so no publisher certificate authenticates this executable.
- MalwareTips.Synth.DirectIpC2 fired after 13 external IP contacts without application domains, and contactedHosts=null prevents determining whether those addresses have harmful reputations.
- communityComments[1] and communityComments[3] report third-party KillMBR assessments, but they have zero votes and are not corroborated by engines, the completed sandbox verdict, or offensive techniques.
- droppedChildren.rollup.unknown=5, so the absence of a known malicious child is not equivalent to five confirmed-clean children.
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 engines reported malicious or suspicious results.
- All 17 tier-1 engines reported no detection.
- 10,937 submissions from 3,660 sources demonstrate established prevalence.
- The completed sandbox run reported offensiveCount=0 and hasMaliciousSandboxVerdict=false.
- Static PE analysis found no packer, high-entropy code, or likely packing.
- The executable is unsigned, so its publisher identity is not cryptographically verified.
- MalwareTips.Synth.DirectIpC2 fired after 13 external IP contacts without corresponding application domains.
- contactedHosts=null means no complete reputation result exists for observed network contacts.
- All five inspected dropped children remain individually unclassified.
- Zero-vote community annotations contain uncorroborated KillMBR assessments.
Use a copy obtained directly from Ventoy's official release channel and compare its SHA-256 hash before execution. Keep antivirus and endpoint protection enabled.
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
Partial20 runtime contacts were observed without a completed reputation cross-check.
YARA
Complete1 signature or behavior rule matched.
External intel
PartialIndependent reference checks were attempted but are incomplete.
Behavior
Plain-English impact first, then the observed runtime evidence.
Runtime flight recorder
Capture complete- 1isolated sandbox run
- 15MITRE ATT&CK techniques
- 15spawned processes
- 20network contacts
- 7filesystem & mutex artifacts
Attack story
Runtime observations grouped by analysis stage. Arrows organize the stages; they do not claim chronology or causality.
Input file
The submitted object
- FileObserved
Ventoy2Disk.exe
aa194a077ff8b57db01ce51cf492201f708e66d89535e80df2748eb13f86b951
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\file.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
%SAMPLEPATH%\Ventoy2Disk.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
log.txt
C:\Users\<USER>\Desktop\log.txt
04Isolated runtime analysis - Written fileObserved
log.txt
C:\Users\<USER>\Downloads\log.txt
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
192.168.0.63
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
20.99.133.109
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 recorded facts from one runtime window. Every fact remains independently traceable in Analyst mode.
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.
- 192.168.0.63
- 20.99.133.109
- 23.55.140.42
- 192.168.0.62
- 23.213.37.172
- a83f:8110:86b5:ffff:3093:630f:86b5:ffff
- 192.168.0.52
- 20.99.186.246
- 23.198.74.242
- 23.46.228.41
- C:\Users\<USER>\Desktop\log.txt
- C:\Users\<USER>\Downloads\log.txt
- C:\Users\user\Desktop\log.txt
- C:\Windows\System32\wbem\Performance\WmiApRpl.h
- C:\Windows\System32\wbem\Performance\WmiApRpl.ini
- C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\Microsoft\Crypto\Keys\de7cf8a7901d2ad13e5c67c29e5d1662_cbbb49d6-b7ff-44ca-aba5-8a5e250d4d42
- %USERPROFILE%\AppData\Local\Microsoft\Windows\INetCache\IE\KLT1I0ZU\update50[1].xml
Files this sample writes at runtime
This file drops 5 children at runtime. None are currently flagged malicious in our cache.
- d61fa9bc636a3643b1fa…08c64cNever scannednever seen before
- cd77640fa5ec03baf2a5…ce9976Never scannednever seen before
- 3da1570c39f8885f0b8f…9bff0cNever scannednever seen before
- c2b7ba21d2065a942aa3…886328Never scannednever seen before
- 740b534223564bc305e3…c91708Never scannednever seen before
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
- 3,660sources 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 a long, established submission history across 3,660 sources.
Verdict inputView chapterProvenanceDerivedSourceSubmission historyObserved at - 03
One or more independent reference checks were incomplete or unavailable.
ProvenanceDerivedSourceExternal-intelligence coverageObserved at - 04
Scanned file: Ventoy2Disk.exe — aa194a077ff8b57db01ce51cf492201f708e66d89535e80df2748eb13f86b951
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\file.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — %SAMPLEPATH%\Ventoy2Disk.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: log.txt — C:\Users\<USER>\Desktop\log.txt
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: log.txt — C:\Users\<USER>\Downloads\log.txt
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 192.168.0.63 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
Contacted host: 20.99.133.109 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
Available reference checks returned no match, but at least one source was unavailable. This is not a clean result.
Signatures and behavior heuristics
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
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.
Evidence20.99.133.109 · 23.55.140.42 · 23.213.37.172
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
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- Ventoy2Disk.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 589.5 KB
- Last analyzed
- Sep 10, 2026, 6:43 PM UTC
aa194a077ff8b57db01ce51cf492201f708e66d89535e80df2748eb13f86b951Safety & 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 Ventoy2Disk.exe safe?
What is Ventoy2Disk.exe?
How many antivirus engines detected Ventoy2Disk.exe?
What is the SHA-256 hash of Ventoy2Disk.exe?
Is it safe to run Ventoy2Disk.exe?
How up to date is this analysis of Ventoy2Disk.exe?
Community
Member reviews and reports for this exact file hash.