Suspicious
Unsigned MSI with clean engine results but sandbox-detected process injection and LSASS access.
afe11244e96c0e3fa8…42836798e5The reasoning behind this verdict
The MT AI Engine weighs every signal from this scan — antivirus detections, sandbox behaviour, code signing, prevalence and historical matches — to reach a single, evidence-based verdict.
Zero malicious detections across 61 reporting engines including all tier-1 vendors rules out widespread malware consensus. However the two offensive MITRE techniques and corresponding synthetic heuristics indicate suspicious runtime activity targeting LSASS and remote thread creation. Being unsigned and only 12 days old with minimal prevalence further reduces trust. The combination of clean static signals and concerning behavioural signals produces a borderline case best classified suspicious rather than safe or malicious.
Each signal cites a concrete token from the evidence the arbiter saw — engine name, MITRE technique, signer string, or an exact count.
engines: 0 malicious out of 75 (Microsoft, BitDefender, Kaspersky, ESET-NOD32 all undetected)
behaviour.offensiveTechniques: T1055, T1548 observed in sandbox
triggeredHeuristics[0]: MalwareTips.Synth.ProcessInjection fired (evidence: svchost.exe)
prevalence.classification: rare_new with 3 submitters
signing.verified: false (unsigned MSI)
- Zero detections from 75 engines
- No malicious dropped children
- No contacted malicious hosts
- Unsigned installer
- Sandbox observed LSASS access
- Process injection techniques recorded
- Rare new prevalence (3 submissions)
Treat as suspicious pending further behavioural analysis or a signed release from the vendor.
What this file does
What it attempted when executed in an isolated sandbox
High concern: Hides inside another running program to evade antivirus.
High concern: Talks to a remote server to take commands or send out your data.
High concern: Can spread through USB and removable drives.
Note: Reads your Windows user-account details.
Note: Collects details about your system.
Translated from the file's technical behaviour during analysis. It never ran on your device.
What to do now
We couldn't fully clear this file. Treat it with caution.
Don't run it unless you're certain it came from a source you trust.
Check where you got it — an email attachment or a random download link is a red flag.
If you're unsure, delete it. You can always re-download a clean copy from the official source.
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
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.
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.log
- C:\Windows\Temp\~DF76BEA12B2B1B07C9.TMP
- C:\Windows\Temp\~DF761DEE14FD02EB44.TMP
- C:\Windows\Temp\~DFB1B372B70F233664.TMP
- C:\Windows\Temp\~DFD250934D3081A0A9.TMP
- C:\Config.Msi\CMPE1C4.tmp
- C:\Config.Msi
- C:\Windows\Installer\dc97.msi
- C:\Config.Msi\CMPE55E.tmp
- C:\Config.Msi\dc96.rbs
- Global\_MSIExecute
- \BaseNamedObjects\Local\SM0:6996:304:WilStaging_02
Files this sample writes at runtime
This file drops 8 children at runtime. None are currently flagged malicious in our cache.
- 8fdc8d3d12876b6c9dc8…9a3191Never scannednever seen before
- 24aa985d01d4123e0b3f…e17263Never scannednever seen before
- 01960077670b151ba514…ea9708Never scannednever seen before
- 31ef6d0daf229a90ed46…ceee49Never scannednever seen before
- ca286b2289d28013520c…8704bbNever scannednever seen before
- 325b0aa212d9245293f0…25922cNever scannednever seen before
- dd591596e8f8f1658e75…eea0d2Never scannednever seen before
- 1c119febd5f388f46b91…37a319Never scannednever seen before
YARA & heuristic rule matches
A researcher-curated or high-severity heuristic rule matched this sample. These rules target specific malware families and are near-definitive.
MITRE T1055 (Process Injection) observed — CreateRemoteThread / APC / reflective-DLL injection. The payload is being smuggled into a legitimate process to bypass AV hooks.
EvidenceC:\Windows\System32\svchost.exe -k NetworkService -pSandbox 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.exe
0 detections across 75 engines
How widely this file has been seen
Barely seen in the wild and first surfaced recently. This is the footprint of targeted malware the AV industry hasn't signatured yet — extra scrutiny is warranted.
Forensic fingerprint
- File name
- HardwareVisualizer_1.8.1_x64_en-US.msi
- Size
- 6.16 MB
- MIME type
- (unknown)
- Detected type
- Windows Installer
- SHA-256
- afe11244e96c0e3fa8d60b1c58a587aa5cb063eac18a2d075d498842836798e5
- MD5
- c2e2b57ddcf92a2d9ad6bf9018ead90e
- SHA-1
- f0a687430a41b5f04bd26b39502b36e1d4ca1730
- First seen (VT)
- 5/11/2026, 4:41:38 AM
- Last analysis (VT)
- 5/12/2026, 6:34:40 AM
- First scan (MalwareTips)
- 5/23/2026, 7:26:28 AM
- Last scan (MalwareTips)
- 5/23/2026, 7:26:28 AM
Safety FAQ
Common questions about HardwareVisualizer_1.8.1_x64_en-US.msi, answered from the scan data above.
- HardwareVisualizer_1.8.1_x64_en-US.msi is suspicious — treat it as unsafe until you're sure. 0 of 75 antivirus engines flag it, 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.
- HardwareVisualizer_1.8.1_x64_en-US.msi is a software installer, about 6.2 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.
- None — all 75 antivirus engines we queried report HardwareVisualizer_1.8.1_x64_en-US.msi as clean. That's reassuring, though brand-new malware can briefly evade detection before vendors add signatures, so we also weigh the file's behaviour and reputation.
- 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 HardwareVisualizer_1.8.1_x64_en-US.msi: 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 HardwareVisualizer_1.8.1_x64_en-US.msi 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.
- The SHA-256 hash of HardwareVisualizer_1.8.1_x64_en-US.msi is afe11244e96c0e3fa8d60b1c58a587aa5cb063eac18a2d075d498842836798e5, and its MD5 is c2e2b57ddcf92a2d9ad6bf9018ead90e. 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 May 23, 2026. Because a file's hash never changes, the identity of HardwareVisualizer_1.8.1_x64_en-US.msi 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.