Is MXB-App-0.13.7-x64.exe safe?
Only one low-trust engine detected this unsigned new executable, but observed process-injection and LSASS-targeting indicators warrant caution until independently verified.
The lone Trapmine detection is probably a false positive because no tier-1 engine flagged the file. However, the completed sandbox run recorded process-injection indicators and activity involving LSASS, while the unsigned executable is newly observed and its direct-IP contact was not reputation-checked.
c1f7f9330d9ae2f6f5…3bdaed3a36898dRecommended 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.
The lone Trapmine detection is probably a false positive because no tier-1 engine flagged the file. However, the completed sandbox run recorded process-injection indicators and activity involving LSASS, while the unsigned executable is newly observed and its direct-IP contact was not reputation-checked.
One of 75 engines flagged the sample, and that result came from the low-trust Trapmine engine rather than a tier-1 detector. This strongly lowers the weight of the antivirus alert. A completed sandbox run nevertheless mapped activity to T1055 and T1134, with an additional heuristic citing LSASS-targeting process activity. The executable is unsigned and newly observed 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 tier-1 engine 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. A separate heuristic also cited process activity targeting LSASS, which can be associated with credential access, although the sandbox itself did not issue a malicious verdict. The sample contacted 162.159.36.2 directly, but no completed reputation cross-check is available for that address. Ten dropped children 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 endpoint protection enabled and, if testing is necessary, use an isolated disposable environment with no credentials or sensitive data.
Where this verdict could be wrong4 caveats
- engines.onlyLowTrustFlagging=true and 14 tier-1 engines reported no detection, strongly suggesting the lone Trapmine result may be a false positive.
- behaviour.hasMaliciousSandboxVerdict=false, and droppedChildren.hasMaliciousChild=false after 10 children were inspected.
- externalIntel.yaraify.ruleCount=0, externalIntel.circl.hit=false, and externalIntel.malwareBazaar.hit=false, although absence of matches does not establish benignity.
- peAnalysis.highEntropyCode=false and peAnalysis.likelyPacked=false 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/75 engines detected the file, and the detection came from low-trust Trapmine
- engines.tier1Malicious=0 with 14 tier-1 engines reporting no detection
- behaviour.hasMaliciousSandboxVerdict=false
- droppedChildren.hasMaliciousChild=false across 10 inspected children
- externalIntel reported no CIRCL, MalwareBazaar, or YARAify match
- Unsigned Win32 executable with no established signer history
- Newly observed file with only 2 sources and 4 submissions
- Sandbox evidence mapped to process injection technique T1055
- LSASS-targeting activity cited by MalwareTips.Synth.CredentialDumper
- Direct connection to 162.159.36.2 without a completed reputation cross-check
Verify SHA-256 c1f7f9330d9ae2f6f59b37093ea0c6ba6f1cc4ae63b687f3773bdaed3a36898d against the developer's official release channel before use. Keep endpoint protection enabled and avoid running it with administrative privileges.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete1 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
Complete3 signature or behavior rules 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
- 23MITRE ATT&CK techniques
- 13spawned processes
- 1network contacts
- 21filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Injected code into another process, a technique that can conceal execution.
High concern: Changed an auto-start location that can make code run after sign-in or restart.
High concern: Manipulated how the operating system loads code, which can redirect execution.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Runs hidden system commands (script or shell).
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Scans through your files and folders.
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
MXB-App-0.13.7-x64.exe
c1f7f9330d9ae2f6f59b37093ea0c6ba6f1cc4ae63b687f3773bdaed3a36898d
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\MXB-App-0.13.7-x64.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
taskkill /F /IM "MXB App.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
nsqCE3D.tmp
C:\Users\<USER>\AppData\Local\Temp\nsqCE3D.tmp
04Isolated runtime analysis - Written fileObserved
System.dll
C:\Users\<USER>\AppData\Local\Temp\nsrCE8D.tmp\System.dll
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>\AppData\Local\Temp\nsqCE3D.tmp
- C:\Users\<USER>\AppData\Local\Temp\nsrCE8D.tmp\System.dll
- C:\Users\<USER>\AppData\Local\Temp\nsrCE8D.tmp\modern-wizard.bmp
- C:\Users\<USER>\AppData\Local\Temp\nsrCE8D.tmp\nsDialogs.dll
- C:\Users\<USER>\AppData\Local\Temp\nsrCE8D.tmp\nsExec.dll
- C:\Users\<USER>\AppData\Local\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\LocalCache\KnownGameList.bin
- C:\Users\<USER>\AppData\Local\Microsoft\GameDVR\KnownGameList.update
- C:\Users\user\AppData\Local\Temp\nseABE0.tmp
- C:\Users\user\AppData\Local\Temp\nshA6CD.tmp
- cversions.3.m
- Global\OneSettingQueryMutex+compat+encapsulation
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- b121689861b506dbc9c3…1c00bbNever scannednever seen before
- da3f122d19f811a0ee68…fde700Never scannednever seen before
- 5150f962e878c051a9c7…291db2Never scannednever seen before
- 415ae373546198d1ecef…4d9af6Never scannednever seen before
- 5d46ff44fc0fbcdfcad9…1ca522Never scannednever seen before
- b1350f487692057c8ffd…551fc0Never scannednever seen before
- 43d1e6be1bbbb9a0d66f…2de400Never scannednever seen before
- 8b4c47c4cf5e76ec57dd…90d37cNever scannednever seen before
- 6722abb3265dc6b8cf32…564fecNever scannednever seen before
- 5ba143b5db4a87d32d6e…ad4709Never 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.
- 3rule hits recorded
- 1 / 75engines flagged
- 2sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
1 high-confidence signature or behavior rule matched this file.
Verdict inputView chapterProvenanceDerivedSourceSignature and behavior rulesObserved at - 02
1 of 75 antivirus engines flagged the file, including Trapmine.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 4 times from 2 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: MXB-App-0.13.7-x64.exe — c1f7f9330d9ae2f6f59b37093ea0c6ba6f1cc4ae63b687f3773bdaed3a36898d
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\MXB-App-0.13.7-x64.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — taskkill /F /IM "MXB App.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: nsqCE3D.tmp — C:\Users\<USER>\AppData\Local\Temp\nsqCE3D.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: System.dll — C:\Users\<USER>\AppData\Local\Temp\nsrCE8D.tmp\System.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
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
A community signature or high-severity behavioral heuristic matched. Signatures identify known patterns; heuristics are strong leads but are not proof on their own.
The saved runtime evidence maps this activity to MITRE T1055 (Process Injection). The mapping supports possible process injection, but it does not prove the exact injection method or the operator's intent.
EvidenceC:\Windows\Explorer.EXESandbox observed process activity targeting LSASS (Windows credential store). Legitimate software has no business reading LSASS memory — this is Mimikatz-shape behaviour.
EvidenceC:\Windows\system32\lsass.exeThe 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
1 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. 1 antivirus detection make that low prevalence materially relevant, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- MXB-App-0.13.7-x64.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 12.6 MB
- Last analyzed
- Sep 9, 2026, 10:18 PM UTC
c1f7f9330d9ae2f6f59b37093ea0c6ba6f1cc4ae63b687f3773bdaed3a36898dSafety & 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 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?
How do I remove 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.