File scan report
Verdict Low Risk
Is Test.
A 58-byte .bat file with zero engine detections but only one submission and no data from the test run.
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.
Treat the file as unverified until more evidence or dynamic analysis is obtained.
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 60 flagged
- Flagged 0
- No detection 60
- No result 15
- Code signing Not applicable
- Test run Not run
- First seen 1mo 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
No antivirus engine flagged the file, yet the evidence is too limited for a confident verdict. The batch file is and lacks sandbox or host-reputation results.
Zero malicious detections across 75 engines is a strong clean signal, but the file is only hours old and has a single submission. Similar batch files in the RAG set also received unknown verdicts due to insufficient evidence. Without sandbox execution or contacted-host data, the analysis cannot move beyond low-confidence unknown.
What We Detected
75 engines scanned the 58-byte DOS batch file; none returned a malicious or suspicious result. No code-signing data, sandbox trace, or external-intel hits are present.
Threat Behavior
No behaviour in the test run was observed. The file has not been executed in our sandbox, and no contacted hosts or files it created were recorded.
What To Do Now
Re-scan after more engines have processed the sample or submit it to a sandbox for dynamic analysis before trusting it in any environment.
- 0/60 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 60 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 29, 2026, 7:37 PM UTC
- SHA-256
ea7ed44d92797e7b4bbabefebbd9a548622871b0c4faea7557abe179d7968153- SHA-1
5e5399267d99c3e16e98188191bd35874926af7a- MD5
c51dadebd2adb2811ac78954ba4b97f1
About this file
Test.bat is a DOS batch file file of 58 B.
- Type and size
- DOS batch file · 58 B
- Signer
- Not applicable
- First seen
- Aug 29, 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 Test.bat safe?
What is Test.bat?
How many antivirus engines detected Test.bat?
What is the SHA-256 hash of Test.bat?
How up to date is this analysis of Test.bat?
Community
Member reviews and reports for this exact file hash.