File scan report
Verdict Suspicious
Is Install. exe safe? Treat it as suspicious.
An unsigned installer flagged by 3 of the 71 antivirus engines that checked it with generic labels only; the sandbox runs showed ordinary installer behaviour, but the lack of a…
Read the whole reasonShow less
Why Suspicious? 3 antivirus engines flag it; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
If it came from a link, an attachment or a stranger, delete it.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't install it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already installed it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
Paste this report's link in your topic so helpers can see what was found.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
3 of 71 flagged
- Flagged 3
- No detection 68
- No result 4
- Code signing Unsigned
- Test run Completed
- First seen 3y ago
Chapter 02
Why we think so
4 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
Fortinet and Trellix, two major antivirus engines, plus Webroot flag this unsigned installer with generic rule labels that name no malware family. Nine sandbox runs showed typical installer activity: temporary setup files, bundled audio and graphics libraries, no process injection and no persistence. It has circulated for over three years, yet no publisher identity vouches for it.
Three of the 71 antivirus engines that checked it flag the file, two of them major, but every label is a generic bucket rather than a named family. The installer is unsigned, so no publisher reputation offsets those detections. Across nine sandbox runs it unpacked setup components and libraries in the usual installer pattern, with no high-risk techniques, injection or persistence recorded. It contacted two external IP addresses without a named application domain, a weak lead since no complete host-reputation result covers every contact. Its long history and roughly 100 submitters argue for a false positive, while files built the same way were often bundled with potentially unwanted software.
What We Detected
3 of the 71 antivirus engines that checked it flagged this unsigned Windows installer: Fortinet (W32/PossibleThreat), Trellix (Artemis generic) and Webroot (W32.Malware.Gen). None of the labels names a malware family. Community YARA matches were generic compiler and capability rules only.
Threat Behavior
Nine sandbox runs showed a setup program extracting temporary files, a styling library, an audio library and DirectX helper DLLs. No process injection, persistence or high-risk techniques were recorded. Three dropped components match known-software reference entries. The sample reached two external IP addresses directly; our host-reputation check found nothing malicious among the hosts it covered, though it did not cover every contact.
What To Do Now
Only run this installer if you obtained it from the software's official source. Keep your antivirus enabled, watch for bundled extra offers during setup, and scan the installed program afterwards.
Where this verdict could be wrong2 caveats
- The detections are generic rule-based buckets with no named family. The file has also circulated for over three years among about 100 submitters, and the sandbox recorded no high-risk techniques, which points toward a false positive.
- Three dropped components match known-software reference entries.
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 high-risk techniques, injection or persistence in nine sandbox runs
- Seen for over three years by about 100 submitters
- Three dropped components match known-software reference entries
- No malware-specific YARA rules matched
- Two major antivirus engines flag the file, though with generic labels
- The installer carries no publisher signature
- It contacted external IP addresses without a named application domain
- Installers built the same way have often bundled potentially unwanted software
6 sources checked · all complete. See every source
Chapter 03
What it did in our test
It ran in 9 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 9isolated sandbox runs
- 24sandbox rule tags
- 15spawned processes
- 2network contacts
- 27filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Contains packed or scrambled code that is harder to inspect (common in installers too).
Moderate concern: Ran commands or a script on the test computer.
Moderate concern: Downloaded a file during the test run.
Moderate concern: Unpacked hidden content while it ran.
Moderate concern: Checked whether it was running on a test computer.
Note: Read the user name of the test computer.
Note: Listed the programs running on the test computer.
Sandbox labels we could not confirm (common in safe files too)
Not confirmed: A sandbox rule tagged this run as recording keystrokes; no keylogging was confirmed.
Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.
This file was run on a test computer (a sandbox), not on yours. Labels we could not confirm are listed so you can see them, but they are not treated as evidence against the file.
Recorded behavior
What happened in the test
Grouped by step. The order is not a timeline.
- 1
Input file
The submitted object
- Evidence 1 of 7: FileSeen in the test run
Install.exe
c4142bb2617eade50e8355af3ceb272a4afa70c443ac7824a88923b172b2982c
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
Install.exe
Test run - Evidence 3 of 7: ProcessSeen in the test run
Install.tmp
%USERPROFILE%\AppData\Local\Temp\is-L213K.tmp\Install.tmp
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
_shfoldr.dll
C:\Users\Virtual\AppData\Local\Temp\is-KEOET.tmp\_isetup\_shfoldr.dll
Test run - Evidence 5 of 7: Written fileSeen in the test run
D3DX9_43.dll
C:\Users\Virtual\AppData\Local\Temp\is-KEOET.tmp\D3DX9_43.dll
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostSeen in the test run
209.197.3.8
Contacted during the test run.
Test run - Evidence 7 of 7: Contacted hostSeen in the test run
23.32.75.27
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes the sandbox verdicts, 24 mapped techniques, every process, file, registry and network entry and 10 dropped files.
Show the technical evidenceChapter 04
Technical details
3 of the 71 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · all complete. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 3
- Fortinet (major engine)W32/PossibleThreat
- TrellixENS (major engine)Artemis!3E9A8674CE31
- WebrootW32.Malware.Gen
File fingerprint
- Last analyzed
- Oct 19, 2026, 6:41 AM UTC
- SHA-256
c4142bb2617eade50e8355af3ceb272a4afa70c443ac7824a88923b172b2982c- SHA-1
ef1b87a05f3150b9e1f84bd058375521c7f71571- MD5
3e9a8674ce31441eb5feea8854e7b380
About this file
Install.exe says it is KaOs Repacks™ (KaOs®), 9.7 MB.
- Claims to be
- KaOs Repacks™ (KaOs®)From the file's own version information, written by whoever built it.
- Type and size
- Win32 EXE · 9.7 MB
- Signer
- UnsignedNo code signature.
- First seen
- May 31, 2023On VirusTotal.
- Submitted by
- 101 distinct sources
- Packer
- None detected
- Entropy
- 5.65 of 8
First scanned
Includes every engine result (75), 4 matched signature rules, PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is Install.exe safe, or is it malware?
What is Install.exe?
How many antivirus engines detected Install.exe?
I already downloaded and installed Install.exe — what should I do?
What is the SHA-256 hash of Install.exe?
How up to date is this analysis of Install.exe?
Community
Member reviews and reports for this exact file hash.