File scan report
Verdict Malicious
Is Gen
A ZIP archive holding a 64-bit downloader that 27 of the 65 antivirus engines that checked it flag, several of them naming the Paph or Yomal downloader families.
Read the whole reasonShow less
Strong evidence · Two or more major antivirus engines agree.
Delete this archive without extracting or running it. If it was already executed, run a full antivirus scan, review what was placed in your temporary folders, and change passwords for accounts used on that machine.
What to do now3 steps
This ZIP archive is harmful. Don't open or extract it, and delete it.
If you haven't opened or extracted it
Don't open or extract this archive. Delete the archive and any files you extracted from it, then empty the Recycle Bin or Trash.
If you already opened or extracted it
If you already extracted it, delete the extracted files too and run a full antivirus scan.
If a page it opened asked for a password or card details and you entered them, change that password and call your bank.
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.
Antivirus results
27 of 65 flagged
- Flagged 27
- No detection 38
- No result 10
- Code signing Not applicable
- Test run Completed
- First seen 24d ago
Chapter 02
Why we think so
6 points against it and 0 in its favour, checked against the scan evidence.
The reasoning behind this verdict
This archive contains an executable that 27 of the 65 antivirus engines that checked it call malicious, including nine well-regarded engines such as Kaspersky (Trojan-Downloader.Win32.Paph), Avast, Avira, Symantec and Trend Micro. When opened, the archive unpacks itself and starts a hidden PowerShell routine that extracts further files into a temporary folder. It should not be run.
Twenty-seven of the 65 antivirus engines that checked it flagged this archive, and nine of those come from established vendors; the detections cluster on downloader naming, with Kaspersky, Tencent, Sangfor and alibabacloud all pointing at the Paph or Yomal downloader line. Coverage was good — 65 engines returned a result — so the consensus is not an artefact of thin reporting, and no test-file or security-tool signature explains the flags away. In the sandbox runs the archive extracted itself and launched a hidden PowerShell process that unpacked an additional archive into a temporary directory before a program was started from that folder, which is the classic staged-loader pattern and is why one of our behaviour rules matched. The runtime picture is incomplete: one technique in the summary has no named target process, no sandbox run returned a malicious verdict, and the outbound-host reputation check did not complete, so the case rests on the signature consensus plus the observed hidden-PowerShell staging. Neither the file being widely shared nor an absence of a code signature mitigates anything here. There is no benign reading of a hidden, obfuscated extraction chain inside a game-patcher archive that nine established engines call a downloader.
What We Detected
This is a ZIP archive, first seen on Oct 14, 2026, submitted by 118 distinct sources. Inside it is a 64-bit Windows executable. In the antivirus engines 27 of the 65 antivirus engines that checked it flagged the file, nine of them from established vendors: Kaspersky names Trojan-Downloader.Win32.Paph, Tencent names Win32.Trojan-Downloader.Paph, Sangfor names Downloader.Win32.Paph, alibabacloud and Trend Micro name the related Yomal line, and Avast, Avira, G Data, Ikarus, Sophos, Symantec and Trellix also raise alarms. Of the engines that returned a verdict, 23 are independent of one another, so this is not one scanning engine being copied across brand names.
Threat Behavior
The sandbox runs show the archive being unpacked and a second stage launched from a user temporary folder. A PowerShell process was started with its window hidden and with an inline command that expanded a further archive into a temporary directory and queried the Windows version; the main program was then executed from that temporary location. Hidden PowerShell used purely to unpack and stage files is a common way to keep a downloader's real payload out of sight, and one of our behaviour rules matched this pattern. The runs also created keyboard and mouse hook objects of the kind AutoHotkey scripts use, wrote a log and a temporary text file, and checked the machine it was running on.
What To Do Now
Do not open or run the archive, and do not extract its contents manually to "check" them — the executable inside is the component the engines flag. Delete the download if you still have it, and if you have already run it, run a full scan with your security software and change passwords for accounts used on that machine. Keep security software enabled; tools of this kind commonly ask for exclusions or for antivirus to be switched off, and that request should never be granted.
Where this verdict could be wrong2 caveats
- BitDefender and Dr.Web were among the engines that reported nothing, and no sandbox run returned a malicious verdict, so the case rests mainly on static signature detections rather than observed hostile runtime action.
- The contacted-host reputation cross-check did not complete, so any outbound connections the sample may have made were never mapped to known-bad infrastructure.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 27 of the 65 antivirus engines that checked it flag this archive, including nine established vendors and 23 independent detections.
- Several engines name a known downloader family (Paph / Yomal), which indicates a second-stage payload fetched at run time.
- When executed, the archive starts a PowerShell process with a hidden window that extracts additional archives into a temporary folder before running a program from that location.
- The program is launched from a user temporary directory rather than a normal install location, a common staging pattern for loaders.
- The runs created keyboard and mouse hook objects and wrote auxiliary files consistent with an automated patcher/launcher that runs with the user's full privileges.
- The file is unsigned and not tied to any identifiable publisher, so there is no way to verify who built or distributed it.
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 3 isolated tests; no test environment rated what it did as risky.
Test run summary
Capture complete- 3isolated sandbox runs
- 24sandbox rule tags
- 9spawned processes
- 0network contacts
- 19filesystem & 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: Checked whether it was running on a test computer.
Moderate concern: Hid files or windows on the test computer.
Note: Read the user name of the test computer.
Note: Listed the programs running on the test computer.
Note: Deleted files or logs during the test run (installers often clean up after themselves).
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 contacting a server, but no contacted host was recorded.
Not confirmed: A sandbox rule tagged this run as downloading a file, but no download was recorded.
Not confirmed: A sandbox rule tagged this run as weakening security settings; no setting change was recorded.
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 downloaders work
This file is a delivery vehicle. On its own it can look small and harmless, but its job is to fetch and install the real payload, often a password stealer, ransomware or a bot, from a server the attacker controls.
Bottom line:Because the dangerous part arrives later, early scans can look cleaner than the threat really is.
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 5: FileSeen in the test run
GenPatcher 2.15.zip
b31086ff48aa141ac571ef552e3ec1b80a0f211e56cd25c4606f1008d31a989e
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
powershell.exe
powershell.exe -NoProfile -WindowStyle Hidden -InputFormat None -NonInteractive -Command "$env:PATH = 'C:\Windows\System32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\'; $PSVersionTable"
Test run - Evidence 3 of 5: ProcessSeen in the test run
powershell.exe
powershell.exe -NoProfile -WindowStyle Hidden -InputFormat None -OutputFormat None -NonInteractive -Command "$env:PATH = 'C:\Windows\System32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\'; try { Expand-Archive -LiteralPath 'C:\Users\<USER>\AppData\Local\Temp\GP2\validation.zip' -DestinationPath 'C:\Users\<USER>\AppData\Local\Temp\GP2\' -Force -ErrorAction Stop } catch { $_.Exception.Message | Out-File -LiteralPath 'C:\Users\<USER>\AppData\Local\Temp\GP2\ps-error.txt' -Encoding Unicode }"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
Readme.txt
C:\Users\user\AppData\Local\Temp\uphvw1bw.s5u\Readme.txt
Test run - Evidence 5 of 5: Written fileSeen in the test run
validation.zip
C:\Users\<USER>\AppData\Local\Temp\GP2\validation.zip
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
Includes 24 mapped techniques, every process, file, registry and network entry and 7 dropped files.
Show the technical evidenceChapter 04
Technical details
27 of the 65 antivirus engines that checked it flag it.
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 27
- Avast (major engine)Win64:Malware-gen
- AVG (major engine)Win64:Malware-gen
- Avira (major engine)TR/W64.Malware
- F-Secure (major engine)Trojan.TR/W64.Malware
- GData (major engine)Win64.Trojan.Agent.77GV88
- Ikarus (major engine)Trojan.SuspectCRC
- Kaspersky (major engine)Trojan-Downloader.Win32.Paph.rnv
- Sophos (major engine)Mal/Generic-S
File fingerprint
- Last analyzed
- Nov 6, 2026, 6:06 PM UTC
- SHA-256
b31086ff48aa141ac571ef552e3ec1b80a0f211e56cd25c4606f1008d31a989e- SHA-1
5679b3205a5fd31af28fb074aeae4457f9de637b- MD5
b992d647875823e421a9fb4d66d0587f
About this file
GenPatcher 2.15.zip is a ZIP file of 11.6 MB.
- Type and size
- ZIP · 11.6 MB
- Signer
- Not applicable
- First seen
- Oct 14, 2026On VirusTotal.
- Submitted by
- 118 distinct sources
First scanned
Includes every engine result (75), 2 matched signature rules 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 GenPatcher 2.15.zip a virus?
What is GenPatcher 2.15.zip?
How many antivirus engines detected GenPatcher 2.15.zip?
What should I do if I already opened or extracted GenPatcher 2.15.zip?
How do I remove GenPatcher 2.15.zip?
What kind of malware is GenPatcher 2.15.zip?
What is the SHA-256 hash of GenPatcher 2.15.zip?
How up to date is this analysis of GenPatcher 2.15.zip?
Community
Member reviews and reports for this exact file hash.