Is kt6ib.exe safe?
Unsigned executable with two tier-1 detections and sandbox evidence of process injection plus LSASS access.
Two tier-1 engines flagged the file as malicious while fifteen others reported it clean. Sandbox observed process injection and LSASS access, yet no dropped malicious children or external-intel hits were found.
f85972b6092500ce92…28652df22f162eRecommended 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.
Two tier-1 engines flagged the file as malicious while fifteen others reported it clean. Sandbox observed process injection and LSASS access, yet no dropped malicious children or external-intel hits were found.
The combination of tier-1 detections, unsigned status, and offensive MITRE techniques outweighs the clean majority and lack of external corroboration. Similar imphash files have mixed prior verdicts, reinforcing uncertainty. The absence of a completed host-reputation check and the file's recent first-seen date further limit confidence.
What We Detected
5 of 75 engines flagged the sample, including Microsoft (Trojan:Win32/Wacatac.C!ml) and Sophos (Generic ML PUA). Sandbox execution recorded MITRE techniques T1055 (Process Injection), T1134, and T1485 (Data Encrypted for Impact) plus LSASS memory access.
Threat Behavior
The executable wrote multiple temporary NSIS-related files and dropped a Searchmonkey application bundle. No malicious child files were identified among the ten dropped hashes inspected. No network hosts were contacted during the observed run.
What To Do Now
Do not execute the file. Keep endpoint protection enabled. If the file was downloaded from an untrusted source, delete it and scan the system with current signatures.
Where this verdict could be wrong2 caveats
- engines.tier1ReportedClean=15 and 65 undetected engines provide substantial clean coverage.
- droppedChildren 10/10 unknown with no malicious children observed.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 15 tier-1 engines reported clean
- No malicious dropped children
- No external intelligence hits
- Unsigned executable
- Tier-1 malicious detections present
- Sandbox observed LSASS access and process injection
- Rare and recently observed
Treat the file as untrusted; avoid execution until additional independent verification is available.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete5 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
Complete2 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
- 21MITRE ATT&CK techniques
- 11spawned processes
- 0network contacts
- 23filesystem & 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
kt6ib.exe
f85972b6092500ce923050f343b611a8bcc6d992ca174b41ee28652df22f162e
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\Desktop\Searchmonkey_0.3.3_x64-setup.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\Explorer.EXE
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
nshC370.tmp
C:\Users\<USER>\AppData\Local\Temp\nshC370.tmp
04Isolated runtime analysis - Written fileObserved
System.dll
C:\Users\<USER>\AppData\Local\Temp\nswC380.tmp\System.dll
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 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.
- C:\Users\<USER>\AppData\Local\Temp\nshC370.tmp
- C:\Users\<USER>\AppData\Local\Temp\nswC380.tmp\System.dll
- C:\Users\<USER>\AppData\Local\Temp\nswC380.tmp\modern-wizard.bmp
- C:\Users\<USER>\AppData\Local\Temp\nswC380.tmp\nsDialogs.dll
- C:\Users\<USER>\AppData\Local\Temp\nswC380.tmp\nsis_tauri_utils.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\nsoF406.tmp
- C:\Users\<USER>\AppData\Local\Temp\nstF475.tmp
- C:\Users\user\AppData\Local\Temp\nsn762F.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.
- a599f0895b0e8713fa8a…0edbc1Never scannednever seen before
- b1350f487692057c8ffd…551fc0Never scannednever seen before
- 9baee42d66f715bba878…b40256Never scannednever seen before
- decdd4992f3f1b9a5ef9…64e408Never scannednever seen before
- 8b4c47c4cf5e76ec57dd…90d37cNever scannednever seen before
- 7c77109851fee3441554…69e3b5Never scannednever seen before
- cd687a9a45b70756970e…6e485dNever scannednever seen before
- b7c29fc44f25fd7c2439…1c5aedNever scannednever seen before
- 5ba143b5db4a87d32d6e…ad4709Never scannednever seen before
- 3ad2dc318056d0a2024a…056cf2Never 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.
- 2rule hits recorded
- 5 / 75engines flagged
- 1sources 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
5 of 75 antivirus engines flagged the file, including APEX and Cylance.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 03
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: kt6ib.exe — f85972b6092500ce923050f343b611a8bcc6d992ca174b41ee28652df22f162e
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\Desktop\Searchmonkey_0.3.3_x64-setup.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — C:\Windows\Explorer.EXE
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: nshC370.tmp — C:\Users\<USER>\AppData\Local\Temp\nshC370.tmp
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
File written: System.dll — C:\Users\<USER>\AppData\Local\Temp\nswC380.tmp\System.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: generic-trojan
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.exe
5 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. 5 antivirus detections make that low prevalence materially relevant, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- kt6ib.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 6.0 MB
- Last analyzed
- Aug 10, 2026, 6:30 PM UTC
f85972b6092500ce923050f343b611a8bcc6d992ca174b41ee28652df22f162eSafety & 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 kt6ib.exe safe, or is it malware?
What is kt6ib.exe?
How many antivirus engines detected kt6ib.exe?
I already downloaded and ran kt6ib.exe — what should I do?
How do I remove kt6ib.exe?
What kind of malware is kt6ib.exe?
What is the SHA-256 hash of kt6ib.exe?
How up to date is this analysis of kt6ib.exe?
Community
Member reviews and reports for this exact file hash.