File scan report
Verdict Suspicious
Is mod- bisect- gui- v2. 1. 0- pre6- windows- amd64. exe safe? Treat it as suspicious.
One major antivirus engine flagged the file as Trojan:Win32/Wacatac.B!ml while 71 others stayed silent.
Why Suspicious? 4 antivirus engines flag it; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
If it came from a link, an attachment or a stranger, delete it.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't run it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already ran it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
4 of 71 flagged
- Flagged 4
- No detection 67
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 2mo ago
Chapter 02
Why we think so
3 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The binary is unsigned, and contacted a single IP address without triggering sandbox malice or external-intel corroboration.
The one detection from a major antivirus engine is offset by 16 major clean reports and the absence of any family consensus. Lack of code signing and the file's first-seen status increase uncertainty. These mixed signals place the sample in the suspicious band rather than safe or malicious.
What We Detected
4 of the 71 antivirus engines that checked it reported malicious, including one major antivirus engine (Microsoft) labeling it Trojan:Win32/Wacatac.B!ml. The remaining 67 engines returned undetected. The executable is unsigned and first seen on Aug 23, 2026.
Threat Behavior
Sandbox execution recorded five MITRE techniques common in legitimate software and one direct-IP connection to 162.159.36.2. No malicious sandbox verdict, no dropped malicious files it created, 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 major antivirus engines clean
- No sandbox malice
- No external-intel hits
- No malicious files it created
- Unsigned executable
- Rare and newly observed
- One malicious detection from a major antivirus engine
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- 5sandbox rule tags
- 2spawned processes
- 0network contacts
- 3filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
Note: Read basic details of the test computer, such as its Windows version.
Note: Looked through folders on the test computer (most installers do this).
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 5: FileSeen in the test run
mod-bisect-gui-v2.1.0-pre6-windows-amd64.exe
eb25bcd01b394d762d622378afae81c6be3ed06a6f353e30389c17026ef4b29c
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
mod-bisect-gui-v2.1.0-pre6-windows-amd64.exe
"C:\Users\<USER>\Desktop\mod-bisect-gui-v2.1.0-pre6-windows-amd64.exe"
Test run - Evidence 3 of 5: ProcessSeen in the test run
mod-bisect-gui-v2.1.0-pre6-windows-amd64.exe
"C:\Users\user\Desktop\mod-bisect-gui-v2.1.0-pre6-windows-amd64.exe"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
mod-bisect-gui-2026-08-23_23-10-54.log
C:\Users\<USER>\Desktop\mod-bisect-gui-2026-08-23_23-10-54.log
Test run - Evidence 5 of 5: Written fileSeen in the test run
font_index_v6.cache
C:\Users\<USER>\AppData\Local\font_index_v6.cache
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
Includes 5 mapped techniques, every process, file, registry and network entry and 3 dropped files.
Show the technical evidenceChapter 04
Technical details
4 of the 71 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.
Engines that flagged it 4
- Microsoft (major engine)Trojan:Win32/Wacatac.B!ml
- APEXMalicious
- MaxSecureTrojan.Malware.300983.susgen
- Trapminemalicious.moderate.ml.score
File fingerprint
- Last analyzed
- Aug 23, 2026, 11:19 PM UTC
- SHA-256
eb25bcd01b394d762d622378afae81c6be3ed06a6f353e30389c17026ef4b29c- SHA-1
4e0769978b9c4428bbaeee5f1c2f7b890341c1c9- MD5
e0606cdfbb86e00a53badcd103514600
About this file
mod-bisect-gui-v2.1.0-pre6-windows-amd64.exe is a Win32 EXE file of 15.6 MB.
- Type and size
- Win32 EXE · 15.6 MB
- Signer
- UnsignedNo code signature.
- First seen
- Aug 23, 2026On VirusTotal.
- Submitted by
- 1 sourceRarely seen: few people have submitted this exact file.
- Packer
- None detected
- Entropy
- 6.25 of 8
First scanned
Includes every engine result (75), 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 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?
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.