File scan report
Verdict Low Risk
Is build.
New Dyalog file with zero engine detections but insufficient evidence for a confident verdict.
Why not Safe? Only one source had seen it when we scanned it and no sandbox test run results are available.
Limited evidence · Nothing points to a problem, but little confirms who made it.
Do not execute the file until additional analysis data becomes available; keep all security software active.
Good practice2 tips
Low Risk: no threat found, but we could not fully confirm this file.
Get it from the publisher's own website or app store, not from a re-upload or a link someone sent you.
Keep your security software on, and stop if the file does anything you didn't expect.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 61 flagged
- Flagged 0
- No detection 61
- No result 14
- Code signing Not applicable
- Test run Not run
- First seen 2mo ago
Chapter 02
Why we think so
2 points against it and 2 in its favour, checked against the scan evidence.
The reasoning behind this verdict
All 61 antivirus engines that checked it returned clean results and no external intelligence sources flagged the file. However, the file is only hours old, has a single submission, and no sandbox or host-reputation data is available.
Zero malicious detections across 75 engines, including 17 major antivirus engines, is a strong clean signal. The file type is uncommon and the sample is so historical context is absent. Similar files matched only on filetype also received unknown verdicts due to limited evidence. No sandbox execution data, files it created, or contacted-host reputation results exist to corroborate safety. The combination of clean engine results and missing evidence from the test run leaves the sample in the unknown category.
What We Detected
75 antivirus engines scanned the 1.5 KB Dyalog file and none flagged it as malicious or suspicious. No major antivirus engines raised an alert.
Threat Behavior
No sandbox execution data is available, so behaviour in the test run cannot be assessed. The file has not been observed contacting any network hosts, and no programs it started or dropped files were recorded.
What To Do Now
Because the evidence is limited and the file is treat it with caution until more samples or sandbox results appear. Keep security software enabled and avoid executing untrusted scripts.
- 0/61 engines flagged the file
- no external intelligence hits
- rare and prevalence with only one submission
- no sandbox or contacted-host data available
6 sources checked · 4 complete · 1 not run · 1 not needed or not applicable. See every source
Chapter 03
Technical details
None of the 61 antivirus engines that checked it flag it.
Sources checked
Every check behind this verdict
6 sources checked · 4 complete · 1 not run · 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
- Aug 16, 2026, 5:13 PM UTC
- SHA-256
0f106ae40c06ee3d9ab62802d91792fee9b88af0d12ad1296c4ebc25943c49d1- SHA-1
c5b5bdc6743595bf3e8e58ff4ff116f724406aba- MD5
f3d1ffc6b376fa4a14d705f4ade625f9
About this file
build.bat is a Dyalog file of 1.6 kB.
- Type and size
- Dyalog · 1.6 kB
- Signer
- Not applicable
- First seen
- Aug 16, 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 04
Questions & answers
Short answers to the 5 questions people ask most about this file.
Is build.bat safe?
What is build.bat?
How many antivirus engines detected build.bat?
What is the SHA-256 hash of build.bat?
How up to date is this analysis of build.bat?
Community
Member reviews and reports for this exact file hash.