Is mod-bisect-gui-v2.1.0-pre6-windows-amd64.exe safe?
Unsigned first-seen executable with one tier-1 detection and direct-IP contact but no sandbox malice or external-intel hits.
One tier-1 engine flagged the file as Trojan:Win32/Wacatac.B!ml while 71 others stayed silent. The binary is unsigned, brand-new, and contacted a single IP address without triggering sandbox malice or external-intel corroboration.
eb25bcd01b394d762d…9c17026ef4b29cRecommended next actions
Before running
Do not run it until the source and publisher can be verified independently.
If you already ran it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the developer's official site or an official app store.
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.
One tier-1 engine flagged the file as Trojan:Win32/Wacatac.B!ml while 71 others stayed silent. The binary is unsigned, brand-new, and contacted a single IP address without triggering sandbox malice or external-intel corroboration.
The single tier-1 detection is offset by 16 tier-1 clean reports and the absence of any family consensus. Lack of code signing and the file's first-seen status increase uncertainty. Direct-IP contact triggered a low-severity heuristic, yet sandbox and external-intel sources returned no malicious verdict. These mixed signals place the sample in the suspicious band rather than safe or malicious.
What We Detected
4 of 75 engines reported malicious, including one tier-1 engine (Microsoft) labeling it Trojan:Win32/Wacatac.B!ml. The remaining 67 engines returned undetected. The executable is unsigned and first seen today.
Threat Behavior
Sandbox execution recorded five ambient MITRE techniques and one direct-IP connection to 162.159.36.2. No malicious sandbox verdict, no dropped malicious children, and no external-intel hits were observed.
What To Do Now
Do not run the file on production systems. Re-scan after additional reputation data accumulates or obtain the file from an official source if this is intended software.
Where this verdict could be wrong2 caveats
- sandboxVerdicts empty and hasMaliciousSandboxVerdict=false despite 1 sandbox run
- externalIntel (CIRCL/MalwareBazaar/YARAify) all returned no hits
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Majority of tier-1 engines clean
- No sandbox malice
- No external-intel hits
- No malicious dropped children
- Unsigned executable
- Rare and newly observed
- Single tier-1 malicious detection
- Direct-IP contact without domain
Treat as untrusted until more reputation data or an official publisher signature appears; keep endpoint protection enabled.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete4 of 75 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
- 5MITRE ATT&CK techniques
- 2spawned processes
- 1network contacts
- 3filesystem & mutex artifacts
What this file does
Observed actions and their security significance
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Scans through your files and folders.
Note: Collects details about your system.
Note: Connected to 1 server during sandbox analysis.
These are observed capabilities from an isolated analysis. A technique does not prove malicious intent on its own, and the file never ran on your device.
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
mod-bisect-gui-v2.1.0-pre6-windows-amd64.exe
eb25bcd01b394d762d622378afae81c6be3ed06a6f353e30389c17026ef4b29c
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\mod-bisect-gui-v2.1.0-pre6-windows-amd64.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\user\Desktop\mod-bisect-gui-v2.1.0-pre6-windows-amd64.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
mod-bisect-gui-2026-08-23_23-10-54.log
C:\Users\<USER>\Desktop\mod-bisect-gui-2026-08-23_23-10-54.log
04Isolated runtime analysis - Written fileObserved
font_index_v6.cache
C:\Users\<USER>\AppData\Local\font_index_v6.cache
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\mod-bisect-gui-2026-08-23_23-10-54.log
- C:\Users\<USER>\AppData\Local\font_index_v6.cache
- C:\Users\user\Desktop\mod-bisect-gui-2026-08-23_16-14-15.log
Files this sample writes at runtime
This file drops 3 children at runtime. None are currently flagged malicious in our cache.
- 66511c8cf5aaa9cca3d3…3e1e73Never scannednever seen before
- 37d46810f1f46d17da88…41dd73Never scannednever seen before
- 26160982cc36a6824103…cdc615Never 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
- 4 / 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
4 of 75 antivirus engines flagged the file, including APEX and MaxSecure.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: mod-bisect-gui-v2.1.0-pre6-windows-amd64.exe — eb25bcd01b394d762d622378afae81c6be3ed06a6f353e30389c17026ef4b29c
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\Desktop\mod-bisect-gui-v2.1.0-pre6-windows-amd64.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — "C:\Users\user\Desktop\mod-bisect-gui-v2.1.0-pre6-windows-amd64.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: mod-bisect-gui-2026-08-23_23-10-54.log — C:\Users\<USER>\Desktop\mod-bisect-gui-2026-08-23_23-10-54.log
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: font_index_v6.cache — C:\Users\<USER>\AppData\Local\font_index_v6.cache
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
4 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. 4 antivirus detections make that low prevalence materially relevant, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- mod-bisect-gui-v2.1.0-pre6-windows-amd64.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 14.8 MB
- Last analyzed
- Aug 23, 2026, 11:19 PM UTC
eb25bcd01b394d762d622378afae81c6be3ed06a6f353e30389c17026ef4b29cSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't run it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this file and use a fresh copy from a trusted source. Get a fresh copy from the developer's official site or an official app store.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
Is mod-bisect-gui-v2.1.0-pre6-windows-amd64.exe safe, or is it malware?
What is mod-bisect-gui-v2.1.0-pre6-windows-amd64.exe?
How many antivirus engines detected mod-bisect-gui-v2.1.0-pre6-windows-amd64.exe?
I already downloaded and ran mod-bisect-gui-v2.1.0-pre6-windows-amd64.exe — what should I do?
How do I remove mod-bisect-gui-v2.1.0-pre6-windows-amd64.exe?
What is the SHA-256 hash of mod-bisect-gui-v2.1.0-pre6-windows-amd64.exe?
How up to date is this analysis of mod-bisect-gui-v2.1.0-pre6-windows-amd64.exe?
Community
Member reviews and reports for this exact file hash.