File scan report
Verdict Low Risk
Is wabbajack- cli. bat safe? Not fully confirmed.
Tiny 43-byte batch file submitted when we scanned it on Aug 26, 2026 with zero engine detections and no prior reputation.
Read the whole reasonShow less
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 sandbox results become available.
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
1 point against it and 2 in its favour, checked against the scan evidence.
The reasoning behind this verdict
No antivirus engine flagged the file and no sandbox or external-intel data exists. The sample is and extremely small, so the evidence is insufficient for a definitive verdict.
All 61 antivirus engines that checked it returned clean results, including 17 major antivirus engines. The file is a 43-byte DOS batch script first seen on Aug 26, 2026, placing it in the rare and prevalence bucket. Similar batch files previously examined also lacked enough data for classification. Without sandbox execution or external-intel corroboration, the evidence remains too thin to move beyond unknown.
What We Detected
Zero detections from 75 engines; file is a 43-byte .bat with no code signing. No sandbox trace, files it created, or external-intel hits are available.
Threat Behavior
No data from the test run exists. The file's size and age prevent meaningful static or behavioural conclusions.
What To Do Now
Re-scan after more engines have processed the sample or obtain sandbox results before trusting the script.
- 0/61 engines flagged the file
- no external intelligence hits
- rare and prevalence with only one submission
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 26, 2026, 11:04 PM UTC
- SHA-256
206440a46e4d46d9868d7121a4e568142ac30aa94f6c9842fcd4daa5f21f9eee- SHA-1
1868a7b58e2e2d4dfa2fa4946ed821715d074197- MD5
7bbd2e483ed843dc2175c8fe0222b465
About this file
wabbajack-cli.bat is a DOS batch file file of 43 B.
- Type and size
- DOS batch file · 43 B
- Signer
- Not applicable
- First seen
- Aug 26, 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 wabbajack-cli.bat safe?
What is wabbajack-cli.bat?
How many antivirus engines detected wabbajack-cli.bat?
What is the SHA-256 hash of wabbajack-cli.bat?
How up to date is this analysis of wabbajack-cli.bat?
Community
Member reviews and reports for this exact file hash.