Is mtkclient_installer_windows.exe safe?
Only 3 of 74 engines raised generic or grayware alerts, but the unsigned installer and unverified direct-IP contact warrant caution.
Most antivirus evidence favors a false positive: no tier-1 engine detected the file, no named malware family emerged, and the sandbox produced no malicious verdict. However, the executable is unsigned and contacted an IP whose reputation was not checked, so it should be obtained only from the project's official release channel and verified before execution.
47b56e120c5bd744bb…27ff1759e7a088Recommended next actions
Before installing
Do not install it until the source and publisher can be verified independently.
If you already installed it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Download a fresh installer 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.
Most antivirus evidence favors a false positive: no tier-1 engine detected the file, no named malware family emerged, and the sandbox produced no malicious verdict. However, the executable is unsigned and contacted an IP whose reputation was not checked, so it should be obtained only from the project's official release channel and verified before execution.
Three of 74 engines flagged the sample, but none of the 17 reporting tier-1 engines did so, and the detections do not agree on a malware family. One completed sandbox run showed no offensive-only techniques or malicious sandbox verdict, while the written PyQt6 components fit a packaged Python GUI. The sample nevertheless lacks a verified signature and publisher history. It also contacted 162.159.36.2 directly, and no complete host-reputation result is available because the contacted-host check was not saved. Prior files sharing the imphash received cautious assessments, but they have different filenames and no signer co-match, making a shared packaging framework a plausible explanation. Overall, the evidence leans toward generic heuristic or grayware false positives, with unresolved provenance and network-contact concerns preventing stronger reassurance.
What We Detected
Three of 74 antivirus engines flagged the executable. CrowdStrike used a grayware label, while APEX and Bkav returned generic malicious labels; none identified a consistent malware family. All 17 reporting tier-1 engines, including Avast, BitDefender, ESET-NOD32, and Kaspersky, reported no detection.
Threat Behavior
One sandbox run recorded 13 techniques common to installers and packaged applications, but no offensive-only techniques and no malicious sandbox verdict. The file extracted PyQt6 and Microsoft runtime components into a temporary directory, which is consistent with a bundled Python application. It contacted 162.159.36.2 directly, but the host-reputation cross-check was not completed or saved, so that connection cannot be characterized as benign or malicious.
What To Do Now
The executable is unsigned and has no established signer history. Download it only from the official project repository or its explicitly linked release channel, compare its SHA-256 value with a developer-published checksum when available, and keep endpoint protection enabled. If the source or hash cannot be verified, avoid running it on a primary system.
Where this verdict could be wrong4 caveats
- The executable is unsigned despite signing.applicable=true, and signing.signerStats.found=false provides no publisher history.
- CrowdStrike's grayware detection and the direct connection to 162.159.36.2 remain concerns, particularly because contactedHosts was not checked or saved.
- The three prior imphash matches were also marked suspicious, although their different filenames and absent signer co-match substantially weaken that similarity.
- The community comment carries tags including 'blankgrabber' and 'cobalt-strike', but adversarialInputFlags.commentInjectionSuspected=false does not make those uncorroborated tags authoritative, and no engines confirmed either family.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- tier1Malicious=0 and 17 tier-1 engines reported no detection
- No tier-1 family consensus or confirmed hacktool label
- behaviour.offensiveCount=0 and no malicious sandbox verdict
- droppedChildren.hasMaliciousChild=false across 10 inspected children
- No MalwareBazaar, CIRCL, or YARAify corroboration
- Unsigned Win32 executable with no signer history
- 3/74 antivirus engines reported generic malware or grayware
- Direct connection to 162.159.36.2 lacks a completed reputation check
- Three imphash-only historical matches received cautious assessments
- No developer-published checksum or signature is present in the evidence
Verify SHA-256 47b56e120c5bd744bb51a1fc6bad3acafcd335df60194a2b5c27ff1759e7a088 against an official project release before running it. Keep endpoint protection enabled and avoid execution if its origin cannot be confirmed.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete3 of 74 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial1 runtime contact was observed without a completed reputation cross-check.
YARA
Complete1 signature or behavior rule 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
- 13MITRE ATT&CK techniques
- 4spawned processes
- 1network contacts
- 16filesystem & mutex artifacts
What this file does
Observed actions and their security significance
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: 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: Scans through your files and folders.
Moderate concern: Checked the environment for virtualisation or analysis tools.
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
mtkclient_installer_windows.exe
47b56e120c5bd744bb51a1fc6bad3acafcd335df60194a2b5c27ff1759e7a088
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\mtkclient_installer_windows.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
mtkclient_installer_windows.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
MSVCP140.dll
C:\Users\<USER>\AppData\Local\Temp\_MEI31402\PyQt6\Qt6\bin\MSVCP140.dll
04Isolated runtime analysis - Written fileObserved
MSVCP140_1.dll
C:\Users\<USER>\AppData\Local\Temp\_MEI31402\PyQt6\Qt6\bin\MSVCP140_1.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\_MEI31402\PyQt6\Qt6\bin\MSVCP140.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI31402\PyQt6\Qt6\bin\MSVCP140_1.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI31402\PyQt6\Qt6\bin\MSVCP140_2.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI31402\PyQt6\Qt6\bin\Qt6Core.dll
- C:\Users\<USER>\AppData\Local\Temp\_MEI31402\PyQt6\Qt6\bin\Qt6Gui.dll
- Local\SessionImmersiveColorMutex
Files this sample writes at runtime
This file drops 10 children at runtime. None are currently flagged malicious in our cache.
- c20ad45b3c2891d9f7a5…b3e43dNever scannednever seen before
- a4a6f28f2be50a9698c4…2326d8Never scannednever seen before
- b4015c5d519b4fe93c00…2feae7Never scannednever seen before
- c585918fb1d4821a054e…ac7e8fNever scannednever seen before
- 8c98b5ee246e18397d0d…5b34deNever scannednever seen before
- f41e33e1d790bd0d3eb1…e66867Never scannednever seen before
- 005b0aa0c9a5b930dfdd…bea13dNever scannednever seen before
- 81da2f88cd624097581f…542d28Never scannednever seen before
- fc9e4146f33be3d09b23…3a61a7Never scannednever seen before
- c4f03a873f96edd8ab9c…8319c7Never 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.
- 1rule hit recorded
- 3 / 74engines flagged
- 224sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
3 of 74 antivirus engines flagged the file, including APEX and Bkav.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 241 times from 224 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: mtkclient_installer_windows.exe — 47b56e120c5bd744bb51a1fc6bad3acafcd335df60194a2b5c27ff1759e7a088
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "C:\Users\<USER>\Desktop\mtkclient_installer_windows.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — mtkclient_installer_windows.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: MSVCP140.dll — C:\Users\<USER>\AppData\Local\Temp\_MEI31402\PyQt6\Qt6\bin\MSVCP140.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: MSVCP140_1.dll — C:\Users\<USER>\AppData\Local\Temp\_MEI31402\PyQt6\Qt6\bin\MSVCP140_1.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
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
Low-severity pattern matches — worth noting but not on their own cause for alarm.
The 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
3 of 74 engines flagged this file
View all 74 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
- mtkclient_installer_windows.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 35.9 MB
- Last analyzed
- Sep 21, 2026, 7:35 AM UTC
47b56e120c5bd744bb51a1fc6bad3acafcd335df60194a2b5c27ff1759e7a088Safety & 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 install 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. Download a fresh installer 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 mtkclient_installer_windows.exe safe, or is it malware?
What is mtkclient_installer_windows.exe?
How many antivirus engines detected mtkclient_installer_windows.exe?
What should I do if I already installed mtkclient_installer_windows.exe?
How do I remove mtkclient_installer_windows.exe?
What is the SHA-256 hash of mtkclient_installer_windows.exe?
How up to date is this analysis of mtkclient_installer_windows.exe?
Community
Member reviews and reports for this exact file hash.