File scan report
Verdict Suspicious
Is Velo Strap V0. 2. 1. zip safe? Treat it as suspicious.
ZIP archive containing a PE that triggered three offensive MITRE techniques and direct-IP contacts, yet only one less reliable engine flagged it.
Read the whole reasonShow less
Why Suspicious? One antivirus engine (Bkav) flags it; nothing else confirms it.
Limited evidence · One sign points to a problem; nothing else confirms it.
Treat as suspicious pending further sandbox or reputation data; keep all security software active.
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
1 of 66 flagged
- Flagged 1
- No detection 65
- No result 9
- Code signing Not applicable
- Test run Completed
- First seen 3mo ago
Chapter 02
Why we think so
3 points against it and 3 in its favour, checked against the scan evidence.
The reasoning behind this verdict
One less reliable engine (Bkav) flagged the sample; 16 major antivirus engines remained silent.
The single less reliable detection is outweighed by the absence of major flags, yet the sandbox behaviour (T1055, T1486, plus direct-no complete contacted-host reputation result was available portable software. Medium prevalence and lack of external-intel corroboration leave the file in mixed-signal territory. No complete host-reputation cross-check is available, so contacted-IP risk cannot be fully assessed.
What We Detected
75 engines scanned the ZIP; only Bkav returned a malicious label.
Threat Behavior
The observed MITRE techniques and direct-IP traffic raise concern, but no major antivirus engines corroborated malice and no files for files it created were flagged malicious. Coverage of contacted-host reputation is incomplete.
What To Do Now
Do not execute the contained executable without additional verification. Keep security software enabled and consider re-scanning after more engines or sandbox runs complete.
Where this verdict could be wrong2 caveats
- No major antivirus engines flagged it and only less reliable engines flagged it — single less reliable detection often false positive.
- No sandbox returned a malicious verdict and no dropped file is known to be malicious — no sandbox or child confirmation of malice.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Zero malicious detections from major antivirus engines
- No malicious files it created
- Medium prevalence over 34 days
- Sandbox observed T1055, T1486, T1562.001
- Direct-IP contacts without domain names
- Single less reliable detection may be rule-based noise
6 sources checked · 5 complete · 1 partial. 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- 11sandbox rule tags
- 4spawned processes
- 1network contact
- 16filesystem & 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 the user name of the test computer.
Note: Talked to servers over the internet during the test run.
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 code injection, but no injected program was recorded.
Not confirmed: Showed activity a sandbox rule links to file encryption; no ransomware behaviour was confirmed.
Not confirmed: A sandbox rule tagged this run as weakening security settings; no setting change was recorded.
Not confirmed: A sandbox rule tagged this run as changing how Windows loads code; nothing confirms it.
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 6: FileSeen in the test run
VeloStrap V0.2.1.zip
94b2901a1a4edfc022dceff1a1d6166a8cd6f0efc861a7d3b08eb279ec3de550
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 6: ProcessSeen in the test run
VeloStrap.exe
"C:\Users\<USER>\AppData\Local\Temp\VeloStrap.exe"
Test run - Evidence 3 of 6: ProcessSeen in the test run
cmd.exe
C:\Windows\system32\cmd.exe /c "ver"
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 6: Written fileSeen in the test run
_avif.cp314-win_amd64.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI53282\PIL\_avif.cp314-win_amd64.pyd
Test run - Evidence 5 of 6: Written fileSeen in the test run
_imaging.cp314-win_amd64.pyd
C:\Users\<USER>\AppData\Local\Temp\_MEI53282\PIL\_imaging.cp314-win_amd64.pyd
Test run - +1 more recorded observation
- 1
Network
Hosts contacted
- Evidence 6 of 6: Contacted hostSeen in the test run
185.199.110.133
Contacted during the test run.
Test run
6 facts from the test run. See the full activity list.
Includes 11 mapped techniques, every process, file, registry and network entry and 3 dropped files.
Show the technical evidenceChapter 04
Technical details
1 of the 66 antivirus engines that checked it flags it.
Sources checked
Every check behind this verdict
6 sources checked · 5 complete · 1 partial. Complete means the check returned a usable result; it does not mean the file is safe.
Engines that flagged it 1
- BkavW32.Malware.8389FFF4
File fingerprint
- Last analyzed
- Aug 31, 2026, 8:53 AM UTC
- SHA-256
94b2901a1a4edfc022dceff1a1d6166a8cd6f0efc861a7d3b08eb279ec3de550- SHA-1
33e7b09fb4b1934c3d77093e97cdc56138d0f38c- MD5
86b8a50cc18e65a15ab039c80bb94d7b
About this file
VeloStrap V0.2.1.zip is a ZIP file of 51.5 MB.
- Type and size
- ZIP · 51.5 MB
- Signer
- Not applicable
- First seen
- Jul 28, 2026On VirusTotal.
- Submitted by
- 68 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 6 questions people ask most about this file.
Is VeloStrap V0.2.1.zip safe, or is it malware?
What is VeloStrap V0.2.1.zip?
How many antivirus engines detected VeloStrap V0.2.1.zip?
I already downloaded and opened or extracted VeloStrap V0.2.1.zip — what should I do?
What is the SHA-256 hash of VeloStrap V0.2.1.zip?
How up to date is this analysis of VeloStrap V0.2.1.zip?
Community
Member reviews and reports for this exact file hash.