File scan report
Verdict Suspicious
Is Velostrap. dll safe? Treat it as suspicious.
Only 1 of the 69 antivirus engines that checked it flagged this file, and that result came from less reliable APEX while all 17 major antivirus engines remained silent.
Read the whole reasonShow less
Why Suspicious? One antivirus engine (APEX) flags it; nothing else confirms it.
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 run 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 ran 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 69 flagged
- Flagged 1
- No detection 68
- No result 5
- Code signing Unsigned
- Test run Completed
- First seen 8mo ago
Chapter 02
Why we think so
3 points against it and 5 in its favour, checked against the scan evidence.
The reasoning behind this verdict
The antivirus pattern strongly favors a false positive: APEX supplied the only detection among 74 engines, with no major detections or family consensus. The sample is also widely encountered, with 1,879 sources and 2,415 submissions over 222 days. The completed host-reputation cross-check covered all distinct observed domains and IPs and found no known malicious or suspicious hosts, while no inspected child was identified as malicious. Because the file is unsigned and the similar-file history is mixed and based only on import-table fingerprint matches without signer corroboration, the evidence does not support a fully benign conclusion.
What We Detected
APEX was the sole detector among 74 antivirus engines. No major antivirus engines flagged the sample, and no engine consensus identified a malware family. The file has also been submitted 2,415 times by 1,879 sources, which is inconsistent with a narrowly distributed threat lacking broader detection.
Threat Behavior
One completed sandbox run did not produce a malicious sandbox verdict, but the saved evidence mapped activity to MITRE T1055 process injection and raised the Windows password store-access heuristic. Those behaviors can be security-sensitive and should not be ignored. All 19 distinct observed hosts were covered by the host-reputation check, with none known as malicious or suspicious, and no inspected file it created was identified as malicious. The executable is unsigned, so there is no verified publisher identity to help explain the behavior.
What To Do Now
Keep security software enabled and obtain the file only from its official project or vendor channel. Verify its SHA-256 value and expected release provenance before running it; if its source cannot be established, quarantine or remove it rather than executing it on a production system.
Where this verdict could be wrong3 caveats
- The saved runtime mapping includes process injection and a rule-based indicating access to the Windows password store, activities that warrant caution even though the sandbox did not issue a malicious verdict.
- The missing code signature leaves the executable without a verifiable publisher.
- Three unknown file it created outcomes remain in the dropped-file summary, although none of the four inspected children was identified as malicious.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- Only 1 of the 69 antivirus engines that checked it flagged the sample, and the detector was less reliable.
- All 17 major antivirus engines reported no detection.
- The sample has 1,879 unique sources and 2,415 submissions.
- All 19 distinct observed hosts were checked, with no known malicious or suspicious results.
- No inspected file it created was identified as malicious.
- The executable is unsigned and has no established signer history.
- APEX flagged the file as malicious.
- Three inspected child hashes lack conclusive cached verdicts.
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- 9sandbox rule tags
- 4spawned processes
- 23network contacts
- 17filesystem & 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: Checked whether it was running on a 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: Loaded extra code modules while running.
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.
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 7: FileSeen in the test run
Velostrap.dll
6fd8ae68be5e103a957250c32eae71d6a5f6495ac85ffe7d5a278d1474fe154e
Uploaded file
- 2
Processes
What ran
- Evidence 2 of 7: ProcessSeen in the test run
Velostrap.exe
"C:\Users\<USER>\Desktop\Velostrap.exe"
Test run - Evidence 3 of 7: ProcessSeen in the test run
msedge.exe
"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --single-argument https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=6.0.0&arch=x64&rid=win-x64&os=win10&gui=true
Test run - +1 more recorded observation
- 2
Files
Created or changed
- Evidence 4 of 7: Written fileSeen in the test run
S-1-15-2-543634040-274359014-2226501544-3561766748-3991453649-3543631192-522786984
\Device\NamedPipe\Sessions\1\AppContainerNamedObjects\S-1-15-2-543634040-274359014-2226501544-3561766748-3991453649-3543631192-522786984
Test run - Evidence 5 of 7: Written fileSeen in the test run
BITF45D.tmp
C:\Users\<USER>\AppData\Local\Temp\edge_BITS_7120_871742141\BITF45D.tmp
Test run - +1 more recorded observation
- 2
Network
Hosts contacted
- Evidence 6 of 7: Contacted hostWorked out from other results
aka.ms
Older reputation report (safe), not counted as current evidence.
Contacted-host cross-check - Evidence 7 of 7: Contacted hostSeen in the test run
js.monitor.azure.com
Contacted during the test run.
Test run - +1 more recorded observation
7 facts from the test run. See the full activity list.
Includes the sandbox verdicts, 9 mapped techniques, every process, file, registry and network entry and 3 dropped files.
Show the technical evidenceChapter 04
Technical details
1 of the 69 antivirus engines that checked it flags it; no publisher signature.
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
- APEXMalicious
File fingerprint
- Last analyzed
- Oct 1, 2026, 3:51 PM UTC
- SHA-256
6fd8ae68be5e103a957250c32eae71d6a5f6495ac85ffe7d5a278d1474fe154e- SHA-1
1d90e950c46b54fb676791768ef6fe0551a513bb- MD5
72a63c8f2b6314ca6c58c75f6d71d462
About this file
Velostrap.dll is a Win32 EXE file of 13.9 MB.
- Type and size
- Win32 EXE · 13.9 MB
- Signer
- UnsignedNo code signature.
- First seen
- Feb 21, 2026On VirusTotal.
- Submitted by
- 1,879 distinct sources
- Packer
- None detected
- Entropy
- 5.72 of 8
First scanned Updated
Includes every engine result (74), 1 matched signature rule, PE section entropy and packers 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.dll safe, or is it malware?
What is Velostrap.dll?
How many antivirus engines detected Velostrap.dll?
I already downloaded and ran Velostrap.dll — what should I do?
What is the SHA-256 hash of Velostrap.dll?
How up to date is this analysis of Velostrap.dll?
Community
Member reviews and reports for this exact file hash.