File scan report
Verdict Malicious
Is Open Vape- v4. 21. 4- hotfix. zip safe? No, we rate this exact file malicious.
Thirty-one of the 60 antivirus engines that checked it flagged this injector archive, while evidence from the test run mapped process injection, service execution, and…
Read the whole reasonShow less
Strong evidence · Two or more major antivirus engines agree.
If you already opened or extracted it, follow the steps below.
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
31 of 60 flagged
- Flagged 31
- No detection 29
- No result 15
- Code signing Not applicable
- Test run Completed
- First seen 1mo ago
Chapter 02
Why we think so
4 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The archive drew 31 detections among 75 engines, including six major detections and 24 independent engine votes. Execution launched an injector, loaded a native DLL through rundll32, and mapped T1055, T1543.002, and T1562.001, strongly supporting the trojan detections despite one clean sandbox verdict.
Detection is broad: 31 of the 60 antivirus engines that checked it flagged the archive, with six major detections and 24 independent votes. BitDefender identified Yogi, while ESET-NOD32 and Fortinet reported Kryptik-family trojan variants; the exact family naming is not unanimous. The completed runtime run launched Vape421Injector.exe, loaded Vape421Native.dll through rundll32.exe, and mapped process injection, service execution, and defense impairment. The sandbox's clean verdict is meaningful dissent, but it conflicts with both its own recorded activity and the strong antivirus evidence. No complete contacted-host reputation result is available, and the ten dropped files remain unclassified rather than cleared.
What We Detected
Thirty-one of the 60 antivirus engines that checked it flagged the ZIP archive. Six major antivirus engines detected it, and the detections represent 24 independent engine votes after related products were consolidated. BitDefender and several related labels identify Yogi variants, while ESET-NOD32 and Fortinet identify GenKryptik or Kryptik trojans; this supports a trojan assessment even though the family labels are not fully consistent.
Threat Behavior
The completed sandbox run extracted multiple executables, a DLL, a batch file, and a Java service into a temporary directory. It then launched Vape421Injector.exe and used rundll32.exe to load Vape421Native.dll. No target process was identified for the injection mapping, so the precise injection method remains unproven.
The sandbox itself returned a clean verdict, and no malware-specific external research rule corroborated the sample. However, these counter-signals do not outweigh the breadth and quality of detections plus the injector-related activity in the test run. The dropped files have no saved verdicts, and no complete host-reputation cross-check is available.
What To Do Now
Do not extract or execute this archive. Quarantine or delete it while keeping security software enabled. If it was already run, disconnect the affected system from sensitive networks, perform a full security scan, and review services, temporary files, and account activity for unauthorized changes.
Where this verdict could be wrong3 caveats
- The completed sandbox run returned a clean verdict, although it still recorded several offensive-technique mappings and injector-related execution.
- No malware-specific YARAify rule or MalwareBazaar record corroborated the detections.
- None of the ten dropped files has a saved malicious verdict, but all ten remain unclassified rather than cleared.
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 completed sandbox run returned a clean verdict.
- No malware-specific external research rules or sample-feed record corroborated the file.
- No persistence indicators or sample-attributed network contacts were recorded in the completed run.
- Thirty-one of the 60 antivirus engines that checked it flagged the archive, including six major antivirus engines.
- The detections represent 24 independent engine votes rather than only related vendor products.
- Behaviour in the test run launched an injector and loaded a native DLL through rundll32.
- The archive extracted multiple executable components into a temporary directory.
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- 17sandbox rule tags
- 12spawned processes
- 0network contacts
- 15filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
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: Listed the programs running on the test computer.
Note: Read basic details of the test computer, such as its Windows version.
Note: Loaded extra code modules while running.
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 code injection, but no injected program 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 creating a service; no new service 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 trojans work
A trojan pretends to be something useful or harmless so that you run it. Once open, it does its real job in the background, from stealing data to opening a back door or downloading more malware.
Bottom line:The disguise is the whole trick, so a trustworthy-looking name or icon means nothing.
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
OpenVape-v4.21.4-hotfix.zip
64e17d5fbf54b00788a9a06c1ddd6f556399ea5756ce776a8846836951054a5a
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 5: ProcessSeen in the test run
cmd.exe
"C:\Windows\system32\cmd.exe" /c "cd ^"C:\Users\<USER>\AppData\Local\Temp^" && start /wait ^"^" ^"C:\Users\<USER>\AppData\Local\Temp\service.bat^"
Test run - Evidence 3 of 5: ProcessSeen in the test run
cmd.exe
C:\Windows\system32\cmd.exe /K "C:\Users\<USER>\AppData\Local\Temp\service.bat
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
2840
C:\Users\<USER>\AppData\Local\Temp\hsperfdata_<USER>\2840
Test run - Evidence 5 of 5: Written fileSeen in the test run
3903daac9bc4a3b7.timestamp
C:\ProgramData\Oracle\Java\.oracle_jre_usage\3903daac9bc4a3b7.timestamp
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
Includes the sandbox verdicts, 17 mapped techniques, every process, file, registry and network entry and 8 dropped files.
Show the technical evidenceChapter 04
Technical details
31 of the 60 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 31
- BitDefender (major engine)Gen:Variant.Yogi.54915
- Emsisoft (major engine)Gen:Variant.Yogi.54915 (B)
- ESET-NOD32 (major engine)Win64/GenKryptik_AGen.FAC trojan
- F-Secure (major engine)Trojan.TR/W64.MalwareX
- Fortinet (major engine)W64/Kryptik.FAC!tr
- GData (major engine)Gen:Variant.Yogi.53709
- Ikarus (major engine)Trojan.Win64.Krypt
- Sophos (major engine)Mal/Generic-S
File fingerprint
- Last analyzed
- Oct 10, 2026, 9:29 PM UTC
- SHA-256
64e17d5fbf54b00788a9a06c1ddd6f556399ea5756ce776a8846836951054a5a- SHA-1
81a94ff1df28fba4eb73535661ac1f4c5538d0ab- MD5
7efbde431ca89e57ab0f440ab33b1afe
About this file
OpenVape-v4.21.4-hotfix.zip is a ZIP file of 28.3 MB.
- Type and size
- ZIP · 28.3 MB
- Signer
- Not applicable
- First seen
- Sep 5, 2026On VirusTotal.
- Submitted by
- 112 distinct sources
First scanned
Includes every engine result (75), 1 matched signature rule 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 OpenVape-v4.21.4-hotfix.zip a virus?
What is OpenVape-v4.21.4-hotfix.zip?
How many antivirus engines detected OpenVape-v4.21.4-hotfix.zip?
What should I do if I already opened or extracted OpenVape-v4.21.4-hotfix.zip?
How do I remove OpenVape-v4.21.4-hotfix.zip?
What kind of malware is OpenVape-v4.21.4-hotfix.zip?
What is the SHA-256 hash of OpenVape-v4.21.4-hotfix.zip?
How up to date is this analysis of OpenVape-v4.21.4-hotfix.zip?
Community
Member reviews and reports for this exact file hash.