Is Patch.exe safe?
Forty-seven of 75 engines flagged this unsigned patcher, while Microsoft and ESET independently confirmed keygen or hacktool classifications.
The unsigned executable drew 47 detections from 75 engines, including nine high-trust 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.
073e6e9c0a457ced1b…8da609dc553dd5Recommended next actions
Before running
Do not run it. Delete this file from the device, then empty the Recycle Bin or Trash.
If you already ran it
Disconnect from the internet, start a full or offline antivirus scan, then secure important accounts from a clean device.
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.
The unsigned executable drew 47 detections from 75 engines, including nine high-trust 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 75 engines flagged the executable, including nine high-trust detections. Microsoft identified a keygen hacktool, while ESET identified a patcher hacktool, satisfying the confirmed-hacktool threshold. BitDefender, Emsisoft, and GData additionally associated it with Mint stealer heuristics, 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 75 antivirus engines flagged Patch.exe, including nine high-trust 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. One completed sandbox run recorded a DLL written to a Windows service-profile directory and contacts with multiple IP addresses. That sandbox did not independently issue a malicious verdict, and no complete reputation cross-check is available for the contacted hosts, so the 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 endpoint protection 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
- behaviour.hasMaliciousSandboxVerdict=false and behaviour.offensiveCount=0; the single completed sandbox did not independently assign a malicious verdict.
- externalIntel.yaraify.ruleCount=0, externalIntel.circl.hit=false, and externalIntel.malwareBazaar.hit=false, 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.
- engines.tier1FamilyConsensus.strong=false; labels differ among patcher, keygen, generic trojan, PUA, 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 offensive-only MITRE techniques were recorded
- No malicious dropped child was identified
- No current CIRCL, MalwareBazaar, or YARAify hit was saved
- The sample has been widely submitted since 2021
- 47/75 antivirus detections
- Nine high-trust engine detections
- Confirmed patcher or keygen hacktool labels
- Unsigned Win32 executable
- Mint stealer heuristic detections
- DLL written under a Windows service-profile path
Quarantine or delete the file and do not execute it. If it has already run, keep protection enabled and perform a full scan, then reinstall any affected application from its official source.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete47 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Partial20 runtime contacts were 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
- 7MITRE ATT&CK techniques
- 8spawned processes
- 20network contacts
- 26filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Used an input-capture technique that can record credentials or keystrokes.
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: Communicated over a common application protocol; malware can use this for command-and-control.
Moderate concern: Checks which security software you have installed.
Note: Collects details about your system.
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.
Threat context
How hacktools are abused
This is a hacking or cracking tool — the kind used to bypass software licences, generate fake keys, or attack other systems. Even when the tool 'works', these downloads very often carry hidden malware.
Bottom line:Running one means trusting an anonymous author with full access to your PC — rarely worth the risk.
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
Patch.exe
073e6e9c0a457ced1bef8a8c580afa84f8c7ac2156f8032ccc8da609dc553dd5
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"C:\Users\<USER>\AppData\Local\Temp\program.exe"
02Isolated runtime analysis - ProcessObserved
Observed process
%SAMPLEPATH%\073e6e9c0a457ced1bef8a8c580afa84f8c7ac2156f8032ccc8da609dc553dd5.exe
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
udhisapi.dll
C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\Microsoft\UPnP Device Host\upnphost\udhisapi.dll
04Isolated runtime analysis
Network
Hosts contacted
- Contacted hostObserved
a83f:8110:3400:2600:3200:3100:3500:6400
Contact observed during runtime.
05Isolated runtime analysis - Contacted hostObserved
13.107.4.50
Contact observed during runtime.
06Isolated runtime analysis - +1 more recorded observation in Analyst mode
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.
- a83f:8110:3400:2600:3200:3100:3500:6400
- 13.107.4.50
- 23.216.147.64
- a83f:8110:2800:1800:4000:1800:1800:100
- a83f:8110:0:0:64ca:1f00:0:0
- 192.168.0.12
- a83f:8110:0:0:4d82:21:0:0
- 192.168.0.1
- a83f:8110:0:0:0:0:1:0
- a83f:8110:0:0:50c3:a18:a02:0
- C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\Microsoft\UPnP Device Host\upnphost\udhisapi.dll
- C:\Windows\System32\spp\store\2.0\cache\cache.dat
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B19.tmp.WERInternalMetadata.xml
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B2A.tmp.csv
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER6B3B.tmp.txt
- C:\ProgramData\Microsoft\Windows\WER\Temp\WER1008.tmp.WERInternalMetadata.xml
- CTF.LBES.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Compart.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Asm.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.Layouts.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
- CTF.TMD.MutexDefaultS-1-5-21-1482476501-1645522239-1417001333-500
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
- 47 / 75engines flagged
- 526sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
47 of 75 antivirus engines flagged the file, including alibabacloud and Antiy-AVL.
Verdict inputView chapterProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has a long, established submission history across 526 sources.
ProvenanceDerivedSourceSubmission historyObserved at - 03
The hash has been submitted 623 times from 526 sources.
ProvenanceDerivedSourceSaved report factsObserved at - 04
Scanned file: Patch.exe — 073e6e9c0a457ced1bef8a8c580afa84f8c7ac2156f8032ccc8da609dc553dd5
ProvenanceObservedSourceUploaded fileObserved at - 05
Observed process — "C:\Users\<USER>\AppData\Local\Temp\program.exe"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
Observed process — %SAMPLEPATH%\073e6e9c0a457ced1bef8a8c580afa84f8c7ac2156f8032ccc8da609dc553dd5.exe
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: udhisapi.dll — C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\Microsoft\UPnP Device Host\upnphost\udhisapi.dll
ProvenanceObservedSourceIsolated runtime analysisObserved at - 08
Contacted host: a83f:8110:3400:2600:3200:3100:3500:6400 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at - 09
Contacted host: 13.107.4.50 — Contact observed during runtime.
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
Category: hacktool
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
Signatures and behavior heuristics
Behavioral heuristics matched patterns associated with malware. Corroborating evidence determines how much weight they carry.
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.
Evidencea83f:8110:3400:2600:3200:3100:3500:6400 · 13.107.4.50 · 23.216.147.64
47 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
Widely seen in the wild for a long time. High prior this is legitimate; isolated detections on common-old files are usually false positives.
Fingerprint and provenance
- File name
- Patch.exe
- Format
- Win32 EXE
- Code signing
- No verified publisher
- Size
- 970.5 KB
- Last analyzed
- Sep 9, 2026, 5:04 PM UTC
073e6e9c0a457ced1bef8a8c580afa84f8c7ac2156f8032ccc8da609dc553dd5Safety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
This file is dangerous. Treat it as harmful and remove it.
- Recovery step 01
Don't run this file. Delete this file from the device, then empty the Recycle Bin or Trash.
- Recovery step 02
If you already ran it, disconnect from the internet and start with a full antivirus scan or Microsoft Defender Offline scan. If compromise is suspected or the problem persists, use a reputable second-opinion scanner and follow incident-recovery or clean-reinstall guidance.
- Recovery step 03
From a different, clean device, change the passwords on your important accounts (email and banking first) and turn on two-factor authentication.
- Recovery step 04
Get a fresh copy from the developer's official site or an official app store.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
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.