File scan report
Verdict Suspicious
Is MXB-
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.
What this file did when executed
This file was run in a sandbox and its runtime behaviour was observed.
Techniques observed in the sandbox
23MITRE ATT&CK techniques the sandbox mapped. Highlighted ones are rare in normal software; the others are common in legitimate programs too.
- T1010
- T1012
- T1027· Obfuscated code
- T1027.002· Obfuscated code
- T1033· Reads user info
- T1055· Process injection
- T1057· Lists programs
- T1059· Runs commands
- T1071· Application protocol
- T1082· System recon
- T1083· Scans your files
- T1112
- T1115
- T1125
- T1129· Loads modules
- T1134
- T1202
- T1222
- T1497.001· Sandbox evasion
- T1518· Checks your AV
- T1529
- T1547.009· Auto-start
- T1574· Execution hijack
Observed activity
Processes started
4Programs the file ran, with their command lines.
MXB-App-0.13.7-x64.exe"C:\Users\<USER>\Desktop\MXB-App-0.13.7-x64.exe"taskkilltaskkill /F /IM "MXB App.exe"taskkilltaskkill /F /IM "frost.exe"MXB-App-0.13.7-x64.exe"C:\Users\user\Desktop\MXB-App-0.13.7-x64.exe"
Files
19Files the file created, changed or deleted.
- Written
C:\Users\<USER>\AppData\Local\Temp\nsqCE3D.tmp - Written
C:\Users\<USER>\AppData\Local\Temp\nsrCE8D.tmp\System.dll - Written
C:\Users\<USER>\AppData\Local\Temp\nsrCE8D.tmp\modern-wizard.bmp - Written
C:\Users\<USER>\AppData\Local\Temp\nsrCE8D.tmp\nsDialogs.dll - Written
C:\Users\<USER>\AppData\Local\Temp\nsrCE8D.tmp\nsExec.dll - Written
C:\Users\<USER>\AppData\Local\Temp\nsrCE8D.tmp\nsis_tauri_utils.dll
Show all 19 entries for files
- Written
C:\Users\<USER>\AppData\Local\MXB App\MXB App.exe - Written
C:\Users\<USER>\AppData\Local\MXB App\resources\mxbsecure.dll - Written
C:\Users\<USER>\AppData\Local\MXB App\uninstall.exe - Written
C:\Users\<USER>\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\MXB App.lnk - Written
C:\Users\user\AppData\Local\Microsoft\Windows\Caches - Written
C:\Users\user\AppData\Local\Temp - Written
C:\Users\user\AppData\Local\Temp\ - Written
C:\Users\user\AppData\Local\Temp\nseABE0.tmp - Written
C:\Users\user\AppData\Local\Temp\nseABE0.tmp\System.dll - Deleted
C:\Users\<USER>\AppData\Local\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\LocalCache\KnownGameList.bin - Deleted
C:\Users\<USER>\AppData\Local\Microsoft\GameDVR\KnownGameList.update - Deleted
C:\Users\user\AppData\Local\Temp\nseABE0.tmp - Deleted
C:\Users\user\AppData\Local\Temp\nshA6CD.tmp
Mutexes
2Named locks a program uses so only one copy runs; malware families often reuse them.
cversions.3.mGlobal\OneSettingQueryMutex+compat+encapsulation
Sandbox background — not the file
10The analysis machine's own processes and connections, recorded in every run.
- VM process
Explorer.EXEC:\Windows\Explorer.EXE - VM process
services.exeC:\Windows\system32\services.exe - VM process
svchost.exeC:\Windows\System32\svchost.exe -k NetworkService -p - VM process
svchost.exeC:\Windows\system32\svchost.exe -k UnistackSvcGroup - VM process
svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s StorSvc - VM process
svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted -p -s WdiSystemHost
Show all 10 entries for sandbox background — not the file
- VM process
lsass.exeC:\Windows\system32\lsass.exe - VM process
svchost.exeC:\Windows\system32\svchost.exe -k LocalService -s W32Time - VM process
svchost.exeC:\Windows\system32\svchost.exe -k LocalSystemNetworkRestricted -p - VM host
162.159.36.2
Files this sample writes at runtime
This file drops 7 children at runtime. None are currently flagged malicious in our cache. 7 have no saved verdict and were not checked; that is missing coverage, not a finding.
- b121689861b506dbc9c3…1c00bbNot checkedno saved verdict
- 5150f962e878c051a9c7…291db2Not checkedno saved verdict
- 415ae373546198d1ecef…4d9af6Not checkedno saved verdict
- 5d46ff44fc0fbcdfcad9…1ca522Not checkedno saved verdict
- 43d1e6be1bbbb9a0d66f…2de400Not checkedno saved verdict
- 6722abb3265dc6b8cf32…564fecNot checkedno saved verdict
- 5ba143b5db4a87d32d6e…ad4709Not checkedno saved verdict
Chapter 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
Antivirus consensus
1 of 63 engines flagged this file
12 of the 75 engines returned no result for this file (file type not supported, or the scan did not finish), so they did not check it.
- Tier-115 engines0flagged
- Tier-232 engines0flagged
- Low-trust16 engines1flagged
View all 75 engine results
- TrapmineMalicious: suspicious.low.ml.score
- AcronisClean
- AhnLab-V3Clean
- AlibabaClean
- alibabacloudClean
- ALYacClean
- Antiy-AVLClean
- APEXClean
- ArcabitClean
- AvastClean
- Avast-MobileNo result
- AVGClean
- AviraClean
- BitDefenderClean
- BitDefenderFalxNo result
- BkavClean
- CAT-QuickHealClean
- ClamAVNo result
- CMCClean
- CrowdStrikeClean
- CTXClean
- CylanceClean
- CynetClean
- DeepInstinctClean
- DrWebClean
- ElasticClean
- EmsisoftClean
- ESET-NOD32Clean
- F-SecureClean
- FortinetClean
- GDataClean
- GoogleNo result
- GridinsoftClean
- huorongClean
- IkarusNo result
- JiangminClean
- K7AntiVirusClean
- K7GWClean
- KasperskyClean
- KingsoftClean
- LionicClean
- MalwarebytesClean
- MaxSecureNo result
- McAfeeDClean
- MicrosoftClean
- MicroWorld-eScanClean
- NANO-AntivirusClean
- PaloaltoClean
- PandaClean
- RisingClean
- SangforClean
- SentinelOneClean
- SkyhighNo result
- SophosClean
- SUPERAntiSpywareClean
- SymantecClean
- SymantecMobileInsightNo result
- TACHYONClean
- tehtrisClean
- TencentClean
- TrellixENSClean
- TrendMicroNo result
- TrendMicro-HouseCallNo result
- TrustlookNo result
- VaristClean
- VBA32Clean
- VIPREClean
- VirITClean
- ViRobotClean
- WebrootClean
- XcitiumClean
- YandexNo result
- ZillyaClean
- ZoneAlarmClean
- ZonerClean
Signatures and behavior heuristics
Low-severity pattern matches — worth noting but not on their own cause for alarm.
VirusTotal's sandbox summary maps this run to MITRE T1055 (Process Injection), but no injected process of the sample's own was recorded (the analysis VM's own WMI adapter, crash handlers and Chrome updater are not counted). VirusTotal maps T1055 on about half of all files no engine flags, so the mapping alone is not evidence of injection.
EvidenceT1055 (sandbox MITRE mapping)
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
Rarely uploaded, and first seen more than two weeks ago. Often niche legitimate software or internal tooling; not a strong malware signal on its own.
Chapter 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.