File scan report
Verdict Suspicious
Is MXB- App- 0. 13. 7- x64. exe safe? Treat it as suspicious.
The lone Trapmine detection is probably a false positive because no major antivirus engines flagged the file.
Why Suspicious? One antivirus engine (Trapmine) flags 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
1 of 63 flagged
- Flagged 1
- No detection 62
- No result 12
- Code signing Unsigned
- Test run Completed
- First seen 1mo 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
One of the 63 antivirus engines that checked it flagged the sample, and that result came from the less reliable Trapmine engine rather than a major detector. This strongly lowers the weight of the antivirus alert. The executable is unsigned and across only two sources, so there is no established publisher history or broad prevalence to offset those runtime concerns. Ten dropped files produced no confirmed malicious child, and no sandbox issued a malicious verdict. The observed IP contact lacks a completed host-reputation cross-check, preventing a stronger conclusion about its network activity.
What We Detected
Trapmine was the only engine to flag the file, producing a generic machine-learning result. No major antivirus engines detected it, so that isolated alert has a high likelihood of being a false positive. The executable is unsigned and was first observed very recently, with only two contributing sources and four submissions.
Threat Behavior
One completed sandbox run recorded techniques mapped to T1055 and T1134. The sample contacted 162.159.36.2 directly, but no completed reputation cross-check is available for that address. Ten files it created were inspected without a confirmed malicious result, though their individual verdicts remain unknown.
What To Do Now
Do not run the executable on a production system until its source and hash can be verified through the developer's official release channel. Keep security software enabled and, if testing is necessary, use an isolated disposable environment with no credentials or sensitive data.
Where this verdict could be wrong4 caveats
- Only less reliable engines flagged it and 14 major antivirus engines reported no detection, strongly suggesting the lone Trapmine result may be a false positive.
- No sandbox returned a malicious verdict, and no dropped file is known to be malicious after 10 children were inspected.
- No community YARA rule matched, the hash is not in the known-software reference database, and the hash is not listed in the MalwareBazaar malware database, although absence of matches does not establish benignity.
- The absence of packed-level code entropy and the absence of packing indicators provide no static indication of packed executable code.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only 1/63 engines detected the file, and the detection came from less reliable Trapmine
- No major antivirus engines flagged it with 14 major antivirus engines reporting no detection
- No sandbox returned a malicious verdict
- No dropped file is known to be malicious across 10 inspected children
- externalIntel reported no CIRCL, MalwareBazaar, or YARAify match
- Unsigned Win32 executable with no established signer history
- File with only 2 sources and 4 submissions
- Sandbox evidence mapped to process injection technique T1055
- Direct connection to 162.159.36.2 without a completed reputation cross-check
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- 23sandbox rule tags
- 4spawned processes
- 0network contacts
- 21filesystem & 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).
Moderate concern: Ran commands or a script on the test computer.
Moderate concern: Checked whether it was running on a test computer.
Note: Read the user name of the test computer.
Note: Listed the programs running on the test computer.
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).
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.
Not confirmed: A sandbox rule tagged this run as contacting a server, but no contacted host was recorded.
Not confirmed: A sandbox rule tagged this run as setting up auto-start; no auto-start entry was recorded.
Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.
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
MXB-App-0.13.7-x64.exe
c1f7f9330d9ae2f6f59b37093ea0c6ba6f1cc4ae63b687f3773bdaed3a36898d
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
MXB-App-0.13.7-x64.exe
"C:\Users\<USER>\Desktop\MXB-App-0.13.7-x64.exe"
Test run - Evidence 3 of 5: ProcessSeen in the test run
taskkill
taskkill /F /IM "MXB App.exe"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
nsqCE3D.tmp
C:\Users\<USER>\AppData\Local\Temp\nsqCE3D.tmp
Test run - Evidence 5 of 5: Written fileSeen in the test run
System.dll
C:\Users\<USER>\AppData\Local\Temp\nsrCE8D.tmp\System.dll
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
Includes 23 mapped techniques, every process, file, registry and network entry and 7 dropped files.
Show the technical evidenceChapter 04
Technical details
1 of the 63 antivirus engines that checked it flags 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 1
- Trapminesuspicious.low.ml.score
File fingerprint
- Last analyzed
- Sep 9, 2026, 10:18 PM UTC
- SHA-256
c1f7f9330d9ae2f6f59b37093ea0c6ba6f1cc4ae63b687f3773bdaed3a36898d- SHA-1
d4a5c77b23595481a08330eb62882c3924b9d445- MD5
aa22247dd2943fb1c2ce49065cc99845
About this file
MXB-App-0.13.7-x64.exe is a Win32 EXE file of 13.2 MB.
- Type and size
- Win32 EXE · 13.2 MB
- Signer
- UnsignedNo code signature.
- First seen
- Sep 9, 2026On VirusTotal.
- Submitted by
- 2 distinct sourcesRarely seen: few people have submitted this exact file.
- Packer
- None detected
- Entropy
- 8.00 of 8
First scanned
Includes every engine result (75), 1 matched signature rule, 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 MXB-App-0.13.7-x64.exe safe, or is it malware?
What is MXB-App-0.13.7-x64.exe?
How many antivirus engines detected MXB-App-0.13.7-x64.exe?
What should I do if I already ran MXB-App-0.13.7-x64.exe?
What is the SHA-256 hash of MXB-App-0.13.7-x64.exe?
How up to date is this analysis of MXB-App-0.13.7-x64.exe?
Community
Member reviews and reports for this exact file hash.