Is HxMIDIToolsInstallerV86.exe safe?
Three generic detections and concerning LSASS and process-injection activity warrant caution, although tier-1 engines, child-file checks, and external intelligence provide no malware confirmation.
The installer produced concerning runtime indicators involving process injection and LSASS access, and it lacks a verified publisher signature. However, only 3 of 75 engines flagged it, no tier-1 engine identified malware, and neither the sandbox verdict nor external intelligence confirmed a family, leaving materially mixed evidence.
86583d18884050cb98…f605b29a4ef1a0Recommended 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 installer produced concerning runtime indicators involving process injection and LSASS access, and it lacks a verified publisher signature. However, only 3 of 75 engines flagged it, no tier-1 engine identified malware, and neither the sandbox verdict nor external intelligence confirmed a family, leaving materially mixed evidence.
Three of 75 engines flagged the executable, but none were tier-1 and their labels do not establish a common malware family. One completed sandbox run mapped activity to T1055, T1485, and T1548, with an additional heuristic indicating possible LSASS access. That behavior is unusual enough to outweigh the otherwise low detection count, particularly because the installer is unsigned and has no publisher history. Conversely, there was no malicious sandbox verdict, no confirmed malicious dropped child, and no external-intelligence match. Host reputation coverage was incomplete because only one host was inspected while two IP addresses and an update URL were observed. The combined evidence supports quarantine and source verification rather than immediate trust or a definitive family attribution.
What We Detected
Three of 75 antivirus engines flagged the executable. APEX and DeepInstinct used generic labels, while Skyhigh reported behavior resembling a Win32 dropper; no tier-1 engine flagged it and no engine family consensus formed. The executable is also unsigned, so there is no verified publisher identity to connect it to a trusted release.
Threat Behavior
One completed sandbox run mapped activity to T1055, T1485, and T1548. A separate heuristic reported activity targeting LSASS, which can indicate attempted credential access, although the saved evidence does not prove the exact method or intent. The file also contacted two IP addresses and an update URL, but the host-reputation check covered only one host and therefore cannot establish a complete network assessment. Ten dropped files were inspected without a confirmed malicious child, though their individual verdicts remained unknown.
What To Do Now
Do not run the installer on a production system until its origin is verified against the software vendor's official download channel and checksum. Keep endpoint protection enabled, quarantine the file, and use an isolated environment for any necessary further testing.
Where this verdict could be wrong5 caveats
- No tier-1 engine flagged the sample: engines.tier1Malicious=0, while 16 tier-1 engines reported it clean.
- behaviour.hasMaliciousSandboxVerdict=false, and the sandbox recorded an update URL under updates.cme-pro.com that may be consistent with installer activity.
- externalIntel.yaraify.ruleCount=0, externalIntel.malwareBazaar.hit=false, and externalIntel.circl.hit=false; these absences may reflect coverage limits rather than establish benignity.
- peAnalysis.highEntropyCode=false and peAnalysis.likelyPacked=false provide no static indication of packed executable code.
- contactedHosts inspected only 1 host despite two contacted IPs and one URL, so its empty maliciousHosts list is incomplete.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- No tier-1 engine flagged the sample
- No malicious sandbox verdict was recorded
- No dropped child was confirmed malicious
- No CIRCL, MalwareBazaar, or YARAify hit was found
- PE code sections were not assessed as packed or unusually high entropy
- Unsigned Win32 installer with no verified publisher history
- Runtime mapping to process injection technique T1055
- Heuristic evidence of LSASS-targeting process activity
- Additional offensive techniques T1485 and T1548
- Three generic or behavioral detections among 75 engines
- Incomplete reputation coverage for observed network contacts
Quarantine the file and obtain a fresh copy only from the vendor's official release channel, verifying its checksum or publisher signature before use. Keep endpoint protection enabled and avoid production execution.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete3 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 of 3 contacted hosts were cross-checked; coverage is incomplete.
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
- 12MITRE ATT&CK techniques
- 13spawned processes
- 3network contacts
- 31filesystem & 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.
Moderate concern: Contained obfuscated or packed code that makes inspection harder.
Moderate concern: Removed execution artefacts or logs, which can conceal activity.
Moderate concern: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Checked the environment for virtualisation or analysis tools.
Note: Collects details about your system.
Note: Loads extra code modules while running.
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
HxMIDIToolsInstallerV86.exe
86583d18884050cb98a2eb18936d35cf41e5b003556f651abcf605b29a4ef1a0
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\HxMIDIToolsInstallerV86.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\is-4JFWMLJMBU.tmp\HxMIDIToolsInstallerV86.tmp" /SL5="$6002C,5188522,949760,C:\Users\<USER>\Desktop\HxMIDIToolsInstallerV86.exe"
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
HxMIDIToolsInstallerV86.tmp
C:\Users\<USER>\AppData\Local\Temp\is-4JFWMLJMBU.tmp\HxMIDIToolsInstallerV86.tmp
04Isolated runtime analysis - Written fileObserved
_setup64.tmp
C:\Users\<USER>\AppData\Local\Temp\is-85E9QQBSXS.tmp\_isetup\_setup64.tmp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
Network
Hosts contacted
- Contacted hostObserved
104.21.39.81
Contact observed during runtime.
06Isolated runtime analysis - Contacted hostObserved
162.159.36.2
Contact observed during runtime.
07Isolated runtime analysis - +1 more recorded observation in Analyst mode
7 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.
- 104.21.39.81
- 162.159.36.2
- https://updates.cme-pro.com/api/apps/hxmidi/windows/versions
- C:\Users\<USER>\AppData\Local\Temp\is-4JFWMLJMBU.tmp\HxMIDIToolsInstallerV86.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-85E9QQBSXS.tmp\_isetup\_setup64.tmp
- C:\Users\<USER>\AppData\Local\Temp\is-85E9QQBSXS.tmp\_isetup\_isdecmp.dll
- C:\Users\<USER>\AppData\Local\Microsoft\Windows\Explorer\iconcache_idx.db
- C:\Users\<USER>\AppData\Local\Microsoft\Windows\Explorer\iconcache_256.db
- C:\Program Files\CME\is-AIZFE1UIGA.tmp
- C:\Program Files\CME\is-PAM5O691EP.tmp
- C:\ProgramData\Microsoft\Windows\Start Menu\Programs\CME\HxMIDI Tools.lnk
- C:\ProgramData\Microsoft\Windows\Start Menu\Programs\CME\HxMIDI Tools.pif
- C:\ProgramData\Microsoft\Windows\Start Menu\Programs\CME\HxMIDI Tools.url
- cversions.3.m
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- 66023a3c3b229b7e11cf…ce3262Never scannednever seen before
- 0bf9a6d7a1051af03c72…4139baNever scannednever seen before
- 8f5b9203a7e521d9c2da…75936aNever scannednever seen before
- 2354b257fdbed9193c43…e4be96Never scannednever seen before
- 7841f78a3b5a989a4d8b…7741a6Never scannednever seen before
- 388a796580234efc95f3…136f95Never scannednever seen before
- 5d281af887138459e654…20b6d8Never scannednever seen before
- 726d0b21ed0170456ea0…d214c8Never scannednever seen before
- 9026cbd92e29522f512e…953619Never scannednever seen before
- 5bc8c7e2e59358127c84…00f203Never 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
- 3 / 75engines flagged
- 7sources 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
3 of 75 antivirus engines flagged the file, including APEX and DeepInstinct.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 9 times from 7 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: HxMIDIToolsInstallerV86.exe — 86583d18884050cb98a2eb18936d35cf41e5b003556f651abcf605b29a4ef1a0
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\HxMIDIToolsInstallerV86.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — "C:\Users\<USER>\AppData\Local\Temp\is-4JFWMLJMBU.tmp\HxMIDIToolsInstallerV86.tmp" /SL5="$6002C,5188522,949760,C:\Users\<USER>\Desktop\HxMIDIToolsInstallerV86.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: HxMIDIToolsInstallerV86.tmp — C:\Users\<USER>\AppData\Local\Temp\is-4JFWMLJMBU.tmp\HxMIDIToolsInstallerV86.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: _setup64.tmp — C:\Users\<USER>\AppData\Local\Temp\is-85E9QQBSXS.tmp\_isetup\_setup64.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 104.21.39.81 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 10
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.
Evidence104.21.39.81 · 162.159.36.2
3 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
Moderate prevalence — neither rare nor common. No strong prior applies.
Fingerprint and provenance
- File name
- HxMIDIToolsInstallerV86.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 6.5 MB
- Last analyzed
- Sep 17, 2026, 10:01 AM UTC
86583d18884050cb98a2eb18936d35cf41e5b003556f651abcf605b29a4ef1a0Safety & 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 HxMIDIToolsInstallerV86.exe safe, or is it malware?
What is HxMIDIToolsInstallerV86.exe?
How many antivirus engines detected HxMIDIToolsInstallerV86.exe?
What should I do if I already ran HxMIDIToolsInstallerV86.exe?
How do I remove HxMIDIToolsInstallerV86.exe?
What is the SHA-256 hash of HxMIDIToolsInstallerV86.exe?
How up to date is this analysis of HxMIDIToolsInstallerV86.exe?
Community
Member reviews and reports for this exact file hash.