MalwareTips

File scan report

Scan another file

Verdict Malicious

Analyzed , 1 month ago

Is OInstall.exe safe? No, we rate this exact file malicious.

KMSAuto hacking tool identification is strongly corroborated by 52 of the 70 antivirus engines that checked it, while evidence from the test run shows attempts to create Windows…

Read the whole reasonShow less

Strong evidence · Two or more major antivirus engines agree.

Remove it unless you use it on purpose

Keep it only if you installed it on purpose for security testing. Otherwise delete it and run a full antivirus scan.

What to do now4 steps

This is a hacking tool. It is risky to keep and run, but finding it is not by itself a sign that the device is infected.

What to do

  1. Don't run it unless you got it on purpose for security testing on systems you own. Delete it, then empty the Recycle Bin.

  2. If you didn't put it on the device yourself, delete it and run a full antivirus scan: something else may have brought it.

  3. Tools like this often come with cracked or pirated software. If it came that way, treat the whole download as unsafe and scan everything it installed.

If you already ran it

  1. Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.

If you opened or installed it

Avoid banking and sign-ins on that device until it is clean. These free MalwareTips guides walk you through it.

Paste this report's link in your topic so helpers can see what was found.

Why we think so

Share this file report

OInstall.exe: Malicious — MalwareTips file scan

The link always shows the latest result for this exact file (its SHA-256 fingerprint).

Reads the latest antivirus results for this file's hash. Nothing is uploaded.

Antivirus results

52 of 70 flagged

  • Flagged 52
  • No detection 18
  • No result 4
FileOInstall.exe11.5 MBSHA-256 6c256b70d4b6…b9a1d9
  • Code signing Signer not verified
  • Test run Completed
  • First seen 5y ago
1 strong detection rule matched this file.

Chapter 02

Why we think so

7 points against it and 4 in its favour, checked against the scan evidence.

MT AI Engine · Verdict analysis

The reasoning behind this verdict

Analyst conclusion

The sample is a confirmed KMSAuto activation hacking tool, identified by 52 of the 70 antivirus engines that checked it and multiple major antivirus engines. A completed sandbox run also recorded commands attempting to exclude temporary payload paths from Windows Defender, so it should not be executed or allowed through security software.

Where this verdict could be wrong5 caveats
  • No sandbox returned a malicious verdict, although the completed run still recorded endpoint-protection exclusion attempts and five offensive techniques.
  • No dropped file is known to be malicious, but all 10 inspected child verdicts are unknown rather than confirmed clean.
  • No community YARA rule matched and the hash is not in the known-software reference database; these absences may reflect intelligence coverage gaps.
  • The file is widely seen and long established with 108 sources and 127 submissions, indicating broad historical circulation rather than trustworthiness.
  • Two communityComments describe the activator as harmless, but both have zero votes and conflict with independently corroborated engine and evidence from the test run.

These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.

6 sources checked · 5 complete · 1 partial. See every source

Chapter 03

What it did in our test

It ran in our isolated test environment; no test environment rated what it did as risky.

Test run summary

Capture complete
  • 41sandbox rule tags
  • 14spawned processes
  • 4network contacts
  • 40filesystem & mutex artifacts

What the test run showed

What the file did on a test computer

Confirmed in the test run

  • Moderate concern: Created a scheduled task so it runs again later.

  • Moderate concern: Set itself to start automatically after a restart.

  • 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: Used an unusual way to talk to a server.

  • Moderate concern: Checked whether it was running on a test computer.

  • Moderate concern: Hid files or windows on the test computer.

Sandbox labels we could not confirm (common in safe files too)

  • Not confirmed: A sandbox rule tagged this run as code injection, but no injected program was recorded.

  • Not confirmed: A sandbox rule tagged this run as recording keystrokes; no keylogging was confirmed.

  • Not confirmed: A sandbox rule tagged this run as spreading through USB drives; nothing confirms it.

  • 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.

Threat context

How hacking tools are used

Hacking tools are programs that can switch off security software, test passwords or attack other computers. Security professionals use them on purpose; criminals also bundle them with malware.

Bottom line:Keep it only if you installed it on purpose, and check how it got onto the device if you didn't.

Recorded behavior

What happened in the test

Grouped by step. The order is not a timeline.

Seen in the test runWorked out from other results

  1. Input file

    The submitted object

    1
    1. Evidence 1 of 7: FileSeen in the test run

      OInstall.exe

      6c256b70d4b68b25a71efaf82e31ca91e009ddbcb3168cca1832d8fd25b9a1d9

      Uploaded file

  2. Processes

    What ran

    2
    1. Evidence 2 of 7: ProcessSeen in the test run

      file.exe

      "C:\Users\<USER>\AppData\Local\Temp\file.exe"

      Test run
    2. Evidence 3 of 7: ProcessSeen in the test run

      cmd.exe

      "C:\Windows\Sysnative\cmd.exe" /c WMIC /NAMESPACE:\\root\Microsoft\Windows\Defender PATH MSFT_MpPreference call Add ExclusionPath="C:\Users\<USER>\AppData\Local\Temp\file.exe"

      Test run
    3. +1 more recorded observation

  3. Files

    Created or changed

    2
    1. Evidence 4 of 7: Written fileSeen in the test run

      VersionDescriptor.xml

      C:\Users\<USER>\AppData\Local\Temp\over288672\VersionDescriptor.xml

      Test run
    2. Evidence 5 of 7: Written fileSeen in the test run

      {E2E62B8C-C5ED-48AC-A97F-8E2AC11BBF2E}

      C:\Users\<USER>\AppData\Local\Temp\over288672\{E2E62B8C-C5ED-48AC-A97F-8E2AC11BBF2E}

      Test run
    3. +1 more recorded observation

  4. Network

    Hosts contacted

    2
    1. Evidence 6 of 7: Contacted hostSeen in the test run

      23.215.176.152

      Contacted during the test run.

      Test run
    2. Evidence 7 of 7: Contacted hostSeen in the test run

      168.62.242.76

      Contacted during the test run.

      Test run
    3. +1 more recorded observation

7 facts from the test run. See the full activity list.

Chapter 04

Technical details

52 of the 70 antivirus engines that checked it flag it; a signature that did not verify.

Sources checked

Every check behind this verdict

6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.

SourceStatusResultChecked
Antivirus enginesVirusTotal · 74 enginesCompleteRisk signal: 52 of 70 engines flagged it · 4 gave no result Details for antivirus engines
Sandbox runVirusTotal sandboxesCompleteRuntime behaviour was recorded Details for sandbox run
Contacted hostsMalwareTips URL scannerPartial4 hosts contacted in the test run had no completed reputation check Details for contacted hosts
Signature rulesYARAify community rules + MalwareTips rulesCompleteRisk signal: 4 MalwareTips behaviour rules Details for signature rules
Malware sample databaseabuse.ch MalwareBazaarCompleteNot listed
Known-software referenceCIRCL hashlookupCompleteNo match

Engines that flagged it 52

  • Avast (major engine)Win32:PUP-gen [PUP]
  • AVG (major engine)Win32:PUP-gen [PUP]
  • BitDefender (major engine)Gen:Variant.Application.HackTool.KMS.216
  • DrWeb (major engine)Program.VKontakteDJ.116
  • Emsisoft (major engine)Gen:Variant.Application.HackTool.KMS.216 (B)
  • ESET-NOD32 (major engine)Win32/HackTool.KMSAuto.E potentially unsafe application
  • Fortinet (major engine)Riskware/KMSAuto
  • GData (major engine)Gen:Variant.Application.HackTool.KMS.216
44 more in the full engine list

File fingerprint

Last analyzed
Sep 10, 2026, 8:32 PM UTC
SHA-256
6c256b70d4b68b25a71efaf82e31ca91e009ddbcb3168cca1832d8fd25b9a1d9
SHA-1
667b5898693c876bece9ef63e4ed368c30a5e7c8
MD5
4f52762f2a4935a4460b4e2004751adb

About this file

OInstall.exe is a Win32 EXE file of 11.5 MB.

Type and size
Win32 EXE · 11.5 MB
Signer
WZTeam (unverified signature)Worth noting: Malware sometimes copies or steals a company's signature, so this does not mean that company made it.
First seen
Oct 5, 2021On VirusTotal.
Submitted by
108 distinct sources
Packer
UPX (section names)Packing hides code; legitimate installers use it too.
Entropy
7.57 of 8A code section is highly compressed or encrypted.

First scanned

Chapter 05

Questions & answers

Short answers to the 9 questions people ask most about this file.

Is OInstall.exe malware?
OInstall.exe is a hacking tool. It is flagged because it can be misused, not because it infects a device by itself. Keep it only if you use it on purpose; otherwise, delete it, then empty the Recycle Bin. 52 of the 70 antivirus engines that checked it flag it, some as KMSAuto.
What is OInstall.exe?
OInstall.exe is a Windows program, about 11.5 MB. It carries no version information saying what it is or who made it. VirusTotal first saw it on Oct 5, 2021.
How many antivirus engines detected OInstall.exe?
52 of the 70 antivirus engines that checked it flag OInstall.exe, including Microsoft and Kaspersky. We weigh which engines flagged it and what else the scan found, not just the count. The rating comes from all the evidence together, not from this count alone.
I already downloaded and ran OInstall.exe — what should I do?
1) If you ran it on purpose, for testing on systems you own, remove it when you are done. 2) If you didn't download it yourself, delete it and run a full antivirus scan: something else may have brought it. 3) If it came with cracked or pirated software, treat that whole download as unsafe, scan everything it installed and change passwords you typed on the device since.
How do I remove OInstall.exe?
To remove OInstall.exe: 1) Delete it, then empty the Recycle Bin. 2) Run a full scan with your antivirus to check that nothing else came with it. 3) Check Settings > Apps and your startup apps for anything you don't recognise.
What kind of program is OInstall.exe?
Antivirus engines classify OInstall.exe as a hacking tool: a program that can switch off security software, test passwords or attack other computers. Engines attribute it to the KMSAuto family.
Is OInstall.exe digitally signed?
It carries a signature in the name of WZTeam that could not be verified. Malware sometimes copies or steals a company's signature, so this does not mean that company made it.
What is the SHA-256 hash of OInstall.exe?
The SHA-256 fingerprint of OInstall.exe is 6c256b70d4b68b25a71efaf82e31ca91e009ddbcb3168cca1832d8fd25b9a1d9, and its MD5 is 4f52762f2a4935a4460b4e2004751adb. Two files with the same SHA-256 are identical, so use it to check you have exactly this file, not just one with the same name.
How up to date is this analysis of OInstall.exe?
This report reflects the scan on Sep 10, 2026. A file's fingerprint never changes, but antivirus engines keep learning, so a rating can change later. To get a newer result, scan the file again: we refresh the antivirus results when the saved ones are out of date.
Chapter 06

Community

Member reviews and reports for this exact file hash.

Related file reports

Other files people checked with the same threat family, and recent reports with the same rating. A matching threat family does not make two files the same: only the SHA-256 fingerprint identifies a file.

All file reports
Scan another
Check a different file
URL instead?
Check if a link is safe
This report and its SHA-256 fingerprint are public, so the next person who checks the same file gets an instant answer; documents and images are listed by type instead of their file name. A file we had not seen before is uploaded to VirusTotal, whose security partners and subscribers can download it; MalwareTips deletes its own copy after the scan. If you ran this file and are worried, scan your device with up-to-date security software.