File scan report
Verdict Malicious
Is Patch. exe safe? No, we rate this exact file malicious.
Forty-seven of the 68 antivirus engines that checked it flagged this unsigned patcher, while Microsoft and ESET independently confirmed keygen or hacking tool classifications.
Read the whole reasonShow less
Strong evidence · Two or more major antivirus engines agree.
If you already ran it, follow the steps below.
What to do now4 steps
This file is harmful. Don't run it, and remove it.
If you haven't run it
Don't run this file. Delete it, then empty the Recycle Bin.
If you already ran it
Disconnect the device from the internet, then run a full antivirus scan. Microsoft Defender Offline (Windows Security > Virus & threat protection > Scan options) also finds malware that hides while Windows runs.
From another device you trust, change the passwords of your important accounts (email and banking first) and turn on two-step verification.
If the scan keeps finding it, or the device still acts strangely, scan again with a second-opinion scanner from another company; if that doesn't fix it, back up your personal files and reinstall Windows.
If you already ran it, do these in order.
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.
- Trojan removal guideClear steps for Windows, Mac and Android. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (opens malwaretips.com in a new tab)
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (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
47 of 68 flagged
- Flagged 47
- No detection 21
- No result 7
- Code signing Unsigned
- Test run Completed
- First seen 5y ago
Chapter 02
Why we think so
7 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The unsigned executable drew 47 detections from 75 engines, including nine major detections. Microsoft and ESET identified confirmed keygen or patcher functionality, while several other engines reported Mint stealer or trojan traits; avoid running it and remove it from the system.
The detection ratio is substantial: 47 of the 68 antivirus engines that checked it flagged the executable, including nine major detections. BitDefender, Emsisoft, and GData additionally associated it with Mint stealer rules, though family naming is not fully consistent. The file is unsigned, leaving no verified publisher evidence to counterbalance those findings. One sandbox did not issue a malicious verdict, but it recorded a DLL write inside a Windows service-profile path and multiple IP contacts; no complete contacted-host reputation result is available.
What We Detected
47 of the 68 antivirus engines that checked it flagged Patch.exe, including nine major detections. Microsoft reported HackTool:Win32/Keygen, ESET-NOD32 reported Win32/HackTool.Patcher.T, and multiple additional engines identified patcher or keygen functionality. BitDefender, Emsisoft, and GData also reported Mint stealer heuristics.
Threat Behavior
The executable is unsigned and therefore has no verified publisher identity. That sandbox did not independently issue a malicious verdict, and no complete reputation cross-check is available for the contacted hosts. No complete contacted-host reputation result was available.
What To Do Now
Do not run the file or use it to patch or activate software. Keep security software enabled, quarantine or delete the executable, and perform a full system scan if it was launched. If execution occurred, reinstall affected software from its official source and review the system for unexpected files or accounts.
Where this verdict could be wrong4 caveats
- No sandbox returned a malicious verdict and no offensive techniques were mapped; the single completed sandbox did not independently assign a malicious verdict.
- No community YARA rule matched, the hash is not in the known-software reference database, and the hash is not listed in the MalwareBazaar malware database, although external-intelligence coverage can miss threats.
- prevalence shows 526 unique sources and 623 submissions since 2021, so this is established rather than newly observed.
- Major antivirus engines do not agree on one malware family; labels differ among patcher, keygen, generic trojan, unwanted program, and Mint stealer.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- The single sandbox produced no malicious sandbox verdict
- No high-risk MITRE techniques were recorded
- No malicious file it created was identified
- No current CIRCL, MalwareBazaar, or YARAify hit was saved
- The sample has been widely submitted since 2021
- 47/68 antivirus detections
- Nine major antivirus engines detections
- Confirmed patcher or keygen hacking tool labels
- Unsigned Win32 executable
- Mint stealer rule-based detections
- DLL written under a Windows service-profile path
6 sources checked · 5 complete · 1 not needed or not applicable. 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- 7sandbox rule tags
- 3spawned processes
- 0network contacts
- 26filesystem & 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).
Note: Read basic details of the test computer, such as its Windows version.
Note: Checked which security software was installed 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 contacting a server, but no contacted host was recorded.
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 password stealers work
A password stealer runs quietly in the background and copies your private data, such as saved passwords, browser cookies, autofill details and crypto wallets, then sends it to criminals. You usually won't notice anything.
Bottom line:Stolen logins are used to break into your accounts or sold in bulk, so change passwords from another device.
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 4: FileSeen in the test run
Patch.exe
073e6e9c0a457ced1bef8a8c580afa84f8c7ac2156f8032ccc8da609dc553dd5
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 4: ProcessSeen in the test run
program.exe
"C:\Users\<USER>\AppData\Local\Temp\program.exe"
Test run - Evidence 3 of 4: ProcessSeen in the test run
073e6e9c0a457ced1bef8a8c580afa84f8c7ac2156f8032ccc8da609dc553dd5.exe
Test run - +1 more recorded observation
- 1
Files
Created or changed
- Evidence 4 of 4: Written fileSeen in the test run
udhisapi.dll
C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\Microsoft\UPnP Device Host\upnphost\udhisapi.dll
Test run
4 facts from the test run. See the full activity list.
Includes 7 mapped techniques and every process, file, registry and network entry.
Show the technical evidenceChapter 04
Technical details
47 of the 68 antivirus engines that checked it flag it; no publisher signature.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 not needed or not applicable. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 47
- Avast (major engine)Win32:Evo-gen [Trj]
- AVG (major engine)Win32:Evo-gen [Trj]
- Avira (major engine)TR/W32.Evo
- BitDefender (major engine)Gen:Heur.Mint.Stealer.1
- Emsisoft (major engine)Gen:Heur.Mint.Stealer.1 (B)
- ESET-NOD32 (major engine)Win32/HackTool.Patcher.T potentially unsafe application
- F-Secure (major engine)Trojan.TR/W32.Evo
- Fortinet (major engine)Riskware/Patcher
File fingerprint
- Last analyzed
- Sep 9, 2026, 5:04 PM UTC
- SHA-256
073e6e9c0a457ced1bef8a8c580afa84f8c7ac2156f8032ccc8da609dc553dd5- SHA-1
e730740a0d30004a2d949c0da811aa684a43463a- MD5
60f3f529c47cd4942be759861fd7adef
About this file
Patch.exe is a Win32 EXE file of 993.8 kB.
- Type and size
- Win32 EXE · 993.8 kB
- Signer
- UnsignedNo code signature.
- First seen
- Apr 27, 2021On VirusTotal.
- Submitted by
- 526 distinct sources
- Packer
- ASPack/ASProtect (section names), ASProtect (VirusTotal tag)Packing hides code; legitimate installers use it too.
- Entropy
- 7.92 of 8A code section is highly compressed or encrypted.
First scanned
Includes every engine result (75), PE section entropy and packers and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 8 questions people ask most about this file.
Is Patch.exe malware?
What is Patch.exe?
How many antivirus engines detected Patch.exe?
I already downloaded and ran Patch.exe — what should I do?
How do I remove Patch.exe?
What kind of malware is Patch.exe?
What is the SHA-256 hash of Patch.exe?
How up to date is this analysis of Patch.exe?
Community
Member reviews and reports for this exact file hash.