Suspicious
Unsigned installer with one tier-1 spyware label, direct-IP contacts, and mixed sandbox annotations.
b233d7baa7c98f3188…3aac3fddd7The verdict, reasoned out.
Not a rules engine. The MT AI Engine reads every signal we collected, weighs them against history, and commits to an answer.
The single tier-1 detection on a rare family name is not strong enough for a malicious verdict on its own. Direct-IP C2 behaviour raises concern, but the file is a common_old NSIS installer with no malicious children or sandbox consensus. Similar imphash matches were previously rated safe, though without signer overlap. The combination of limited detections, unsigned status, and suspicious network pattern places the sample in mixed-signals territory.
Each signal cites a concrete token from the evidence the arbiter saw — engine name, MITRE technique, signer string, or an exact count.
engines.tier1Malicious=1 (Kaspersky) with tier1FamilyConsensus.strong=false
triggeredHeuristics[0].rule=MalwareTips.Synth.DirectIpC2 — 7 direct IPs, 0 domains
signing.verified=false, unsigned NSIS-style installer (hasInstallerHint=true)
similarHashes[0].verdict=safe and similarHashes[1].verdict=safe (imphash match, signerCoMatch=false)
prevalence.classification=common_old, 385 unique sources
- 68 of 69 engines returned clean
- Common_old prevalence with hundreds of prior submissions
- No malicious dropped children or sandbox verdicts
- Single tier-1 spyware detection on rare family
- Direct-IP network contacts without domains
- Unsigned executable
- Community annotations reference RAT / trojan tags
Treat as untrusted until additional independent sandbox reports or a verified publisher signature can be obtained.
xegumumune corroborated by 2 sources
- VT (74 engines)xegumumune
- MT AI Enginexegumumune
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.
- 224.0.0.251
- 20.99.133.109
- 23.55.140.42
- 23.215.176.115
- 23.32.75.5
- 192.168.0.19
- 20.69.140.28
- 23.196.193.245
- 23.216.147.23
- C:\Users\<USER>\AppData\Local\Temp\nsbF5CA.tmp\System.dll
- C:\Users\<USER>\AppData\Local\Temp\nsbF5CA.tmp\modern-wizard.bmp
- C:\Users\<USER>\AppData\Local\Temp\nsbF5CA.tmp\nsDialogs.dll
- C:\Users\<USER>\AppData\Local\Temp\nsbF5CA.tmp\nsis_tauri_utils.dll
- C:\Users\<USER>\AppData\Local\MechvibesDx\mechvibes-dx.exe
- C:\Users\<USER>\AppData\Local\Packages\Microsoft.XboxGamingOverlay_8wekyb3d8bbwe\LocalCache\KnownGameList.bin
- C:\Users\<USER>\AppData\Local\Microsoft\GameDVR\KnownGameList.update
- %USERPROFILE%\AppData\Local\Temp\nsvF33A.tmp\modern-wizard.bmp
- %USERPROFILE%\AppData\Local\Temp\nsvBB4.tmp\modern-wizard.bmp
- %USERPROFILE%\AppData\Local\Temp\nscEA03.tmp\modern-wizard.bmp
- cversions.3.m
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- fe17a424d0e8c66e3f6e…f0316bNever scannednever seen before
- 10704c370493de0277db…0f343fNever scannednever seen before
- 98f05bc7fa9baa149650…872b8dNever scannednever seen before
- abf64cfa14645043a7c3…8d4341Never scannednever seen before
- fee1bd1daaa5efbcb93c…27bc45Never scannednever seen before
- 84c7ae138ff0f6612c07…921724Never scannednever seen before
- 775960107de6b41d9f3a…8cd97cNever scannednever seen before
- 8130560da30ad6f19994…635594Never scannednever seen before
- 385040a63033e211112b…93259bNever scannednever seen before
- 5ef1f010f9a8be4ffe09…c1d266Never scannednever seen before
YARA + heuristic rules that fired
One or more medium-severity heuristic rules matched. Not definitive, but the patterns match known malware behaviour.
Sample contacted 7 external IP address(es) and zero domains. Benign software virtually always uses DNS; no-DNS direct-IP C2 is a strong malware indicator because it bypasses reputation systems and dodges domain-based blocklists.
Evidence20.99.133.109 · 23.55.140.42 · 23.215.176.115
2 detections across 74 engines
Section entropy & packers
Section-level entropy and packer detection from the PE header. Nothing suspicious here — entropy is within the normal range for unpacked code.
How often this file shows up in the wild
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Forensic fingerprint
- File name
- MechvibesDx_0.3.0_x64-setup.exe
- Size
- 62.68 MB
- MIME type
- (unknown)
- Detected type
- Win32 EXE
- SHA-256
- b233d7baa7c98f318836ebba49ce647530711f2130337f0aede13a3aac3fddd7
- MD5
- 2cd8e3cc37ca1ad75b8d263c2f521f2b
- SHA-1
- d1185f2ae275e3dd5d1d642b14d826b10f896daa
- PE imphash
- 56a78d55f3f7af51443e58e0ce2fb5f6
- First seen (VT)
- 6/19/2025, 2:53:34 PM
- Last analysis (VT)
- 7/9/2026, 5:53:23 PM
- First scan (MalwareTips)
- 7/11/2026, 2:24:03 AM
- Last scan (MalwareTips)
- 7/11/2026, 2:24:03 AM
- Community reputation
- -11flagged
Safety FAQ
Common questions about MechvibesDx_0.3.0_x64-setup.exe, answered from the scan data above.
- MechvibesDx_0.3.0_x64-setup.exe is suspicious — treat it as unsafe until you're sure. 2 of 74 antivirus engines flag it (family: xegumumune), which isn't a strong consensus but is enough to be cautious. Don't run it unless you fully trust where it came from, and prefer downloading the software fresh from its official site.
- MechvibesDx_0.3.0_x64-setup.exe is a Windows executable program, about 62.7 MB. We identify a file by its cryptographic hash rather than its name, because the same filename can be reused by completely different files — the hash below is the reliable fingerprint.
- 2 of 74 antivirus engines flagged MechvibesDx_0.3.0_x64-setup.exe, 2 of them as outright malicious. A small number of detections can include false positives, so we weigh which engines flagged it and what else the file does, not just the raw count.
- Act quickly. 1) Disconnect the device from the internet to stop the malware communicating or spreading. 2) Run a full scan with reputable anti-malware software (such as Malwarebytes) and quarantine everything it finds. 3) Change your important passwords from a DIFFERENT, clean device — many threats log keystrokes or steal saved credentials. 4) If you bank or shop on this device, watch closely for fraud and alert your bank. 5) For a confirmed infection, the most reliable fix is to back up your personal files and reinstall the operating system for a clean start.
- To remove MechvibesDx_0.3.0_x64-setup.exe: 1) restart into Safe Mode (Safe Mode with Networking if you need to download a tool) so the malware doesn't auto-start. 2) Run a full scan with reputable anti-malware software and let it quarantine or delete the detections. 3) Delete the original MechvibesDx_0.3.0_x64-setup.exe file and empty the Recycle Bin/Trash. 4) Check your browser extensions, startup items, and scheduled tasks for anything unfamiliar. 5) Reboot and scan again to confirm it's gone. If detections keep coming back, a clean operating-system reinstall is the most dependable cure.
- MechvibesDx_0.3.0_x64-setup.exe is classified as an information stealer/spyware, built to harvest passwords, cookies, and wallet data. Engines attribute it to the xegumumune family. Knowing the family matters because it tells you the likely impact — data theft, remote control, file encryption, or unwanted ads — and guides the cleanup.
- The SHA-256 hash of MechvibesDx_0.3.0_x64-setup.exe is b233d7baa7c98f318836ebba49ce647530711f2130337f0aede13a3aac3fddd7, and its MD5 is 2cd8e3cc37ca1ad75b8d263c2f521f2b. This hash is the file's unique fingerprint — two files with the same SHA-256 are identical. Use it to confirm you're looking at exactly this file (not just one with the same name) when comparing against antivirus databases or a download's published checksum.
- This report reflects the scan run on July 11, 2026. Because a file's hash never changes, the identity of MechvibesDx_0.3.0_x64-setup.exe is fixed — but antivirus coverage improves over time, so a file that looks clean today can pick up detections later (and vice-versa). If you need the latest picture, MalwareTips staff can re-run the analysis from scratch.
Reviews & malware reports(0)
Tell the community what you saw. Tag the sample — Trojan, Adware, False Positive — and share what the file did on your system. Your report helps confirm or dispute the AV verdict.