File scan report
Verdict Suspicious
Is Open Vape- main. zip safe? Treat it as suspicious.
The archive received no detections from 75 antivirus engines, including all 17 participating major antivirus engines, and its sandbox run produced no malicious conclusion.
Read the whole reasonShow less
Why Suspicious? Sandbox evidence includes MITRE T1562.001, associated with impairing defenses.
Limited evidence · One sign points to a problem; nothing else confirms it.
If it came from a link, an attachment or a stranger, delete it.
What to do now4 steps
Some signs point to a problem, but nothing confirms it is harmful. Treat it with caution.
What to do
Don't open or extract it unless you're sure where it came from.
Check where you got it: an unexpected attachment, a link someone sent you or a re-upload is a red flag.
If you can't confirm where it came from, delete it. If you need the program, download it again from the publisher's own website.
If you already opened or extracted it
Stop using it, run a full scan with your antivirus and watch for unexpected behavior or security alerts.
Not sure what to do?
Ask the MalwareTips community before you run it. If you already ran it, follow the cleanup guide.
- Ask for free help on the MalwareTips forumWindows malware removal help, answered by volunteers. (opens malwaretips.com in a new tab)
- Remove malware from WindowsStep-by-step cleanup with free tools. (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
0 of 64 flagged
- Flagged 0
- No detection 64
- No result 11
- Code signing Not applicable
- Test run Completed
- First seen 1mo ago
Chapter 02
Why we think so
5 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
That run recorded T1562.001, the archive is and all four extracted files lack individual verdicts, so execution should be deferred until the contents are verified.
One completed sandbox run did not issue a malicious conclusion and recorded no network contacts, persistence indicators, or malicious child. However, the run mapped activity to T1562.001, a defense-impairment technique that cannot be dismissed as routine archive extraction. The archive also has only one known submission, no similar-file history, and four extracted children whose individual verdicts remain unknown. No complete contacted-host reputation result is available, although no contacts were recorded during this run.
What We Detected
MalwareBazaar, CIRCL, and YARAify supplied no corroborating match or rule hit. The archive is nevertheless with only one known submission and no similar-file history.
Threat Behavior
One sandbox run extracted the archive and launched its start-service.cmd script. The run produced no malicious sandbox conclusion, persistence indicator, or recorded network contact, but it mapped activity to T1562.001, which concerns impairing defenses. Four files were extracted and none was confirmed malicious; however, each still has an unknown individual verdict, and no complete contacted-host reputation result is available.
What To Do Now
Do not run the command script on a primary system until its contents and all extracted files have been reviewed. Keep security software enabled, obtain the archive from a trusted project source, and test only in an isolated environment if execution is necessary.
Where this verdict could be wrong2 caveats
- The file has only 1 submission and was first observed on Aug 28, 2026, so reputation and prevalence are not yet established.
- All four extracted children have unknown individual verdicts, limiting the reassurance provided by the absence of a known-malicious dropped file.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/64 antivirus engines reported a malicious or suspicious result.
- No sandbox returned a malicious verdict across one completed sandbox run.
- No dropped file is known to be malicious for four inspected children.
- YARAify, MalwareBazaar, and CIRCL returned no matching intelligence.
- Sandbox evidence includes MITRE T1562.001, associated with impairing defenses.
- The archive has only one known submission and was first observed on Aug 28, 2026.
- All four extracted children have unknown individual verdicts.
- The archive launches start-service.cmd through cmd.exe.
- No complete contacted-host reputation cross-check is available.
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- 5sandbox rule tags
- 5spawned processes
- 0network contacts
- 8filesystem & mutex artifacts
What the test run showed
What the file did on a test computer
Confirmed in the test run
Moderate concern: Checked whether it was running on a test computer.
Note: Read basic details of the test computer, such as its Windows version.
Note: Looked through folders on the test computer (most installers do this).
Sandbox labels we could not confirm (common in safe files too)
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.
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-main.zip
e53404624fcf458a0c3626f008048a968ebc4d193c8599052160eaba86436a0e
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\OpenVape-main/start-service.cmd^"
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\OpenVape-main/start-service.cmd
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 5: Written fileSeen in the test run
unarchiver.log
C:\Users\user\AppData\Local\Temp\unarchiver.log
Test run - Evidence 5 of 5: Written fileSeen in the test run
yzlg3t3a.mwp
C:\Users\user\AppData\Local\Temp\yzlg3t3a.mwp
Test run - +1 more recorded observation
5 facts from the test run. See the full activity list.
Includes 5 mapped techniques, every process, file, registry and network entry and 4 dropped files.
Show the technical evidenceChapter 04
Technical details
None of the 64 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.
File fingerprint
- Last analyzed
- Sep 10, 2026, 1:10 AM UTC
- SHA-256
e53404624fcf458a0c3626f008048a968ebc4d193c8599052160eaba86436a0e- SHA-1
ec5d1488a83a777455e243d3bf45f53baa7aa01a- MD5
8af7970f30e3e2f51fec8890ba1b4f27
About this file
OpenVape-main.zip is a ZIP file of 8.6 kB.
- Type and size
- ZIP · 8.6 kB
- Signer
- Not applicable
- First seen
- Aug 28, 2026On VirusTotal.
- Submitted by
- 1 sourceRarely seen: few people have submitted this exact file.
First scanned
Includes every engine result (75) and how widely the file has been seen.
Show the technical evidenceChapter 05
Questions & answers
Short answers to the 6 questions people ask most about this file.
Is OpenVape-main.zip safe, or is it malware?
What is OpenVape-main.zip?
How many antivirus engines detected OpenVape-main.zip?
I already downloaded and opened or extracted OpenVape-main.zip — what should I do?
What is the SHA-256 hash of OpenVape-main.zip?
How up to date is this analysis of OpenVape-main.zip?
Community
Member reviews and reports for this exact file hash.