File scan report
Verdict Safe
Is Mine-
None of the 70 antivirus engines that checked it detected malware, and the completed sandbox run found no offensive behavior, malicious verdict, persistence, or confirmed…
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.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 70 flagged
- Flagged 0
- No detection 70
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 2mo ago
Chapter 02
Why we think so
4 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
All 70 antivirus engines that checked it were silent, including 16 major antivirus engines, and one completed sandbox run produced no malicious verdict or offensive technique.
The strongest evidence is broad antivirus agreement: 0 of the 70 antivirus engines that checked it detected the executable, including all 16 reporting major antivirus engines. One completed observation from the test run showed no offensive techniques, persistence indicators, or malicious sandbox verdict. Two dropped files were inspected without a malicious result, although their individual classifications remain unknown. The antivirus analysis found neither packed code nor high-entropy code sections. The main limitations are the absent signature and direct contact with 162.159.36.2, whose reputation was not completely checked.
What We Detected
None of the 70 antivirus engines that checked it flagged the executable, and all 16 reporting major antivirus engines returned undetected results. The file is unsigned, so there is no verified publisher identity, but static inspection did not identify packing or high-entropy code.
Threat Behavior
One completed sandbox run produced no malicious verdict, high-risk technique, persistence indicator, or confirmed malicious child. The program created Mine-imator-related data, project, log, and Sentry paths. It also contacted 162.159.36.2 directly; because the contacted-host reputation check was not completed or saved, that connection cannot be characterized as benign or malicious.
What To Do Now
Use the file only if it came from the expected Mine-imator project or developer release channel. Keep security software enabled, and avoid running it if its source or hash cannot be verified.
Where this verdict could be wrong4 caveats
- The file is unsigned for a Win32 executable, so no verified publisher identity supports the file.
- The sample contacted 162.159.36.2 directly, and the missing contacted-host reputation result means its reputation was not completely checked.
- Both inspected files it created have unknown verdicts rather than affirmative benign classifications.
- The file's tag list includes detect-debug-environment and long-sleeps, which can impede sandbox observation but can also occur in legitimate applications.
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/70 engines reported a malicious or suspicious result.
- All 16 reporting major antivirus engines returned undetected results.
- One sandbox run produced no malicious verdict and no offensive techniques.
- No persistence indicators or malicious files it created were identified.
- The antivirus analysis found no packer, likely packing, or high-entropy code.
- The Win32 executable is unsigned and has no established signer history.
- Observation from the test run recorded direct contact with 162.159.36.2 without a completed host-reputation cross-check.
- The file carries detect-debug-environment and long-sleeps tags.
- Two files it created were inspected but retain unknown individual verdicts.
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- 6sandbox rule tags
- 2spawned processes
- 0network contacts
- 12filesystem & mutex artifacts
Includes 6 mapped techniques, every process, file, registry and network entry and 2 dropped files.
Show the technical evidenceChapter 04
Technical details
None of the 70 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
- Sep 8, 2026, 5:22 PM UTC
- SHA-256
1430adb6307f0d2fee863e15e4acc04df6b1617ac3ddf692372fe4dfbb3ca673- SHA-1
40d614fcd5dbf14e23ccd07fe8bebd49f7b42f8d- MD5
4b6a15ed3566b1423007333558fc0d64
About this file
Mine-imator Vexel Build.exe is a Win32 EXE file of 40.2 MB.
- Type and size
- Win32 EXE · 40.2 MB
- Signer
- UnsignedNo code signature.
- First seen
- Aug 24, 2026On VirusTotal.
- Submitted by
- 5 distinct sourcesRarely seen: few people have submitted this exact file.
- Packer
- None detected
- Entropy
- 6.51 of 8
First scanned
Includes every engine result (74), 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 Mine-imator Vexel Build.exe safe?
What is Mine-imator Vexel Build.exe?
How many antivirus engines detected Mine-imator Vexel Build.exe?
What is the SHA-256 hash of Mine-imator Vexel Build.exe?
Is it safe to run Mine-imator Vexel Build.exe?
How up to date is this analysis of Mine-imator Vexel Build.exe?
Community
Member reviews and reports for this exact file hash.