Is OpenVape-main.zip safe?
No antivirus engine detected this archive, but a defense-impairment technique, limited prevalence, and unresolved extracted files justify caution before running its script.
The archive received no detections from 75 antivirus engines, including all 17 participating tier-1 engines, and its sandbox run produced no malicious conclusion. However, that run recorded T1562.001, the archive is newly observed, and all four extracted files lack individual verdicts, so execution should be deferred until the contents are verified.
e53404624fcf458a0c…60eaba86436a0eRecommended next actions
Before opening or extracting
Do not open or extract it until the source can be verified independently.
If you already opened or extracted it
Stop using it, scan the device, and watch for unexpected behavior or security alerts. Get a fresh copy from the original trusted source and verify its exact hash when possible.
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 archive received no detections from 75 antivirus engines, including all 17 participating tier-1 engines, and its sandbox run produced no malicious conclusion. However, that run recorded T1562.001, the archive is newly observed, and all four extracted files lack individual verdicts, so execution should be deferred until the contents are verified.
Static scanning found no detection from any of 75 engines, including 17 tier-1 engines. 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
None of 75 antivirus engines flagged the ZIP archive, and all 17 participating tier-1 engines reported no detection. MalwareBazaar, CIRCL, and YARAify supplied no corroborating match or rule hit. The archive is nevertheless newly observed, 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 endpoint protection 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 wrong3 caveats
- T1562.001 was observed in the completed sandbox run, indicating possible impairment of defenses and warranting caution despite the absence of engine detections.
- The file has only 1 submission and was first observed 13 days ago, so reputation and prevalence are not yet established.
- All four extracted children have unknown individual verdicts, limiting the reassurance provided by droppedChildren.hasMaliciousChild=false.
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/75 antivirus engines reported a malicious or suspicious result.
- All 17 participating tier-1 engines reported no detection.
- behaviour.hasMaliciousSandboxVerdict=false across one completed sandbox run.
- droppedChildren.hasMaliciousChild=false 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 13 days ago.
- 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.
Avoid launching start-service.cmd until the archive and its four extracted files are independently reviewed. Keep endpoint protection enabled and use an isolated environment if testing is required.
Coverage & freshness
Complete means the check returned a usable result. It does not mean the file is safe.
Antivirus
Complete0 of 75 engines flagged the file.
Sandbox
Complete1 isolated runtime environment contributed observations.
Network
Not runNo contacted-host reputation check is recorded.
No timestamp recordedYARA
CompleteRule evaluation completed with no recorded matches.
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
- 5MITRE ATT&CK techniques
- 6spawned processes
- 0network contacts
- 8filesystem & mutex artifacts
What this file does
Observed actions and their security significance
High concern: Attempted to impair or bypass security controls.
Moderate concern: Scans through your files and folders.
Moderate concern: Checked the environment for virtualisation or analysis tools.
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.
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
OpenVape-main.zip
e53404624fcf458a0c3626f008048a968ebc4d193c8599052160eaba86436a0e
01Uploaded file
Processes
Runtime execution
- ProcessObserved
Observed process
"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^"
02Isolated runtime analysis - ProcessObserved
Observed process
C:\Windows\system32\cmd.exe /K "C:\Users\<USER>\AppData\Local\Temp\OpenVape-main/start-service.cmd
03Isolated runtime analysis - +1 more recorded observation in Analyst mode
Files
Created or changed
- Written fileObserved
unarchiver.log
C:\Users\user\AppData\Local\Temp\unarchiver.log
04Isolated runtime analysis - Written fileObserved
yzlg3t3a.mwp
C:\Users\user\AppData\Local\Temp\yzlg3t3a.mwp
05Isolated runtime analysis - +1 more recorded observation in Analyst mode
5 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.
- C:\Users\user\AppData\Local\Temp\unarchiver.log
- C:\Users\user\AppData\Local\Temp\yzlg3t3a.mwp
- C:\Users\user\AppData\Local\Temp\yzlg3t3a.mwp\OpenVape-main
- C:\Users\user\AppData\Local\Temp\yzlg3t3a.mwp\OpenVape-main\LICENSE
- C:\Users\user\AppData\Local\Temp\yzlg3t3a.mwp\OpenVape-main\README.md
Files this sample writes at runtime
This file drops 4 children at runtime. None are currently flagged malicious in our cache.
- a2010f343487d3f7618a…cf0499Never scannednever seen before
- cf10e95b78833ff7cf59…e1c765Never scannednever seen before
- 636c59f08f30f3871299…52728aNever scannednever seen before
- c1ae4def3cc87db426f0…d9308aNever scannednever seen before
Detection & Forensics
Consensus, attribution, signatures, code structure, prevalence, and identity.
Evidence integrity
Chain of custody for the facts preserved in this report.
- 0rule hits recorded
- 0 / 75engines flagged
- 1sources in submission history
Why these facts are shown
Each statement identifies whether it was directly recorded or derived from saved scan facts.
- 01
0 of 75 antivirus engines flagged the file.
ProvenanceObservedSourceAntivirus analysisObserved at - 02
The hash has been submitted 1 time from 1 source.
ProvenanceDerivedSourceSaved report factsObserved at - 03
Scanned file: OpenVape-main.zip — e53404624fcf458a0c3626f008048a968ebc4d193c8599052160eaba86436a0e
ProvenanceObservedSourceUploaded fileObserved at - 04
Observed process — "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^"
ProvenanceObservedSourceIsolated runtime analysisObserved at - 05
Observed process — C:\Windows\system32\cmd.exe /K "C:\Users\<USER>\AppData\Local\Temp\OpenVape-main/start-service.cmd
ProvenanceObservedSourceIsolated runtime analysisObserved at - 06
File written: unarchiver.log — C:\Users\user\AppData\Local\Temp\unarchiver.log
ProvenanceObservedSourceIsolated runtime analysisObserved at - 07
File written: yzlg3t3a.mwp — C:\Users\user\AppData\Local\Temp\yzlg3t3a.mwp
ProvenanceObservedSourceIsolated runtime analysisObserved at
Detection sources at a glance
The available sources did not agree on a named threat category.
MalwareBazaar, YARAify, and CIRCL hashlookup completed and returned no entries for this hash.
YARA rules
No matchesThe rule pass completed without a saved public match.
0 of 75 engines flagged this file
View all 75 engine results
PE structure
Not applicablePE structure analysis applies to Windows executable formats, not this file type.
How widely this file has been seen
Barely seen in the wild and first surfaced recently. That limits reputation evidence, but rarity alone is not proof of malware.
Fingerprint and provenance
- File name
- OpenVape-main.zip
- Format
- ZIP
- Code signing
- Not applicable to this file type
- Size
- 8.4 KB
- Last analyzed
- Sep 10, 2026, 1:10 AM UTC
e53404624fcf458a0c3626f008048a968ebc4d193c8599052160eaba86436a0eSafety & FAQ
Complete recovery guidance and answers for the next decision.
What to do now
We couldn't fully clear this file. Treat it with caution.
- Recovery step 01
Don't open or extract it unless you're certain it came from a source you trust.
- Recovery step 02
Check where you got it — an unexpected attachment or a random download link is a red flag.
- Recovery step 03
If its origin cannot be confirmed, delete this archive and use a fresh copy from a trusted source. Get a fresh copy from the original trusted source and verify its exact hash when possible.
- Recovery step 04
If you're still unsure, scan it again in a day or two — detections often catch up on newer files.
Safety FAQ
Direct answers grounded in the saved verdict and evidence in this report.
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?
How do I remove OpenVape-main.zip?
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.