Is Mine-imator Vexel Build.exe safe?
None of 74 engines detected malware, and the completed sandbox run found no offensive behavior, malicious verdict, persistence, or confirmed malicious child.
All 74 antivirus engines were silent, including 16 tier-1 engines, and one completed sandbox run produced no malicious verdict or offensive technique. The unsigned status and direct IP contact warrant source verification, particularly because no complete reputation check exists for that address.
1430adb6307f0d2fee…2fe4dfbb3ca673Recommended 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 74 antivirus engines were silent, including 16 tier-1 engines, and one completed sandbox run produced no malicious verdict or offensive technique. The unsigned status and direct IP contact warrant source verification, particularly because no complete reputation check exists for that address.
The strongest evidence is broad antivirus agreement: 0 of 74 engines detected the executable, including all 16 reporting tier-1 engines. One completed runtime observation 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. Static 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 74 antivirus engines flagged the executable, and all 16 reporting tier-1 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, offensive-only 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 endpoint protection enabled, and avoid running it if its source or hash cannot be verified.
Where this verdict could be wrong4 caveats
- signing.signed=false for a Win32 executable, so no verified publisher identity supports the file.
- The sample contacted 162.159.36.2 directly, and contactedHosts=null means its reputation was not completely checked.
- Both inspected dropped children have unknown verdicts rather than affirmative benign classifications.
- file.tags 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/74 engines reported a malicious or suspicious result.
- All 16 reporting tier-1 engines returned undetected results.
- One sandbox run produced no malicious verdict and no offensive techniques.
- No persistence indicators or malicious dropped children were identified.
- Static analysis found no packer, likely packing, or high-entropy code.
- The Win32 executable is unsigned and has no established signer history.
- Runtime observation 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 dropped children were inspected but retain unknown individual verdicts.
Obtain the executable from the expected official release channel and verify its SHA-256 before use. Keep endpoint protection enabled and rescan if new detections or publisher information emerge.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 74 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
- 6MITRE ATT&CK techniques
- 2spawned processes
- 1network contacts
- 12filesystem & 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
Mine-imator Vexel Build.exe
1430adb6307f0d2fee863e15e4acc04df6b1617ac3ddf692372fe4dfbb3ca673
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\software.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\user\Desktop\software.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
65cb1f25-fd4b-44fb-2a40-bf71209af0ce.run.lock
C:\Users\<USER>\Desktop\Data\Libraries\Sentry\65cb1f25-fd4b-44fb-2a40-bf71209af0ce.run.lock
04Isolated runtime analysis - Written fileObserved
log.txt
C:\Users\<USER>\Desktop\Data\log.txt
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
162.159.36.2
Contact observed during runtime.
06Isolated runtime analysis
6 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.
- 162.159.36.2
- C:\Users\<USER>\Desktop\Data\Libraries\Sentry\65cb1f25-fd4b-44fb-2a40-bf71209af0ce.run.lock
- C:\Users\<USER>\Desktop\Data\log.txt
- C:\Users\user\AppData\Roaming\Mine-imator
- C:\Users\user\Desktop\Data
- C:\Users\user\Desktop\Data\Libraries
- C:\Users\<USER>\Desktop\Data\Libraries\Sentry\65cb1f25-fd4b-44fb-2a40-bf71209af0ce.run.lock
- C:\Users\user\Desktop\Data\Libraries\Sentry\ceb62dfc-ea97-4f30-c16d-f6c3941b1038.run.lock
Files this sample writes at runtime
This file drops 2 children at runtime. None are currently flagged malicious in our cache.
- 45aea1bb2061bba88b23…30130fNever scannednever seen before
- 8112c905bbd9332c549e…7c0d19Never 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 / 74engines flagged
- 5sources 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 74 antivirus engines flagged the file.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 6 times from 5 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: Mine-imator Vexel Build.exe — 1430adb6307f0d2fee863e15e4acc04df6b1617ac3ddf692372fe4dfbb3ca673
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\Desktop\software.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — "C:\Users\user\Desktop\software.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: 65cb1f25-fd4b-44fb-2a40-bf71209af0ce.run.lock — C:\Users\<USER>\Desktop\Data\Libraries\Sentry\65cb1f25-fd4b-44fb-2a40-bf71209af0ce.run.lock
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: log.txt — C:\Users\<USER>\Desktop\Data\log.txt
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
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 74 engines flagged this file
View all 74 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- Mine-imator Vexel Build.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 38.4 MB
- Last analyzed
- Sep 8, 2026, 5:22 PM UTC
1430adb6307f0d2fee863e15e4acc04df6b1617ac3ddf692372fe4dfbb3ca673Safety & 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 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.