File scan report
Verdict Safe
Is install_
No antivirus engine detected this widely submitted batch installer, although one sandbox observed defense-related scripting and direct-IP traffic that lacks complete…
Read the whole reasonShow less
Strong evidence · Widely seen for a long time, and nothing harmful found.
Good practice2 tips
We found nothing harmful in this file.
Run it only if it came from the developer's own website or an official app store.
Keep your antivirus and Windows updates switched on.
No scanner can promise a file is 100% safe.
Reads the latest antivirus results for this file's hash. Nothing is uploaded.
Antivirus results
0 of 59 flagged
- Flagged 0
- No detection 59
- No result 15
- Code signing Not applicable
- Test run Completed
- First seen 3y ago
Chapter 02
Why we think so
4 points against it and 4 in its favour, checked against the scan evidence.
The reasoning behind this verdict
All 59 antivirus engines that checked it were free of detections, including 17 major antivirus engines, and the file has accumulated 7,015 submissions over several years. One sandbox recorded and direct-IP traffic, but produced no malicious runtime verdict; because host reputation was not fully checked, the script should still come from a trusted source.
The strongest evidence is the complete absence of detections across 74 antivirus engines, including all 17 participating major antivirus engines. The batch file is also broadly established, with 3,605 submitters and 7,015 submissions since May 2023, which weighs against a newly distributed threat. A completed sandbox run observed one offensive technique, T1562.001, along with otherwise common installer and network activity, but it did not issue a malicious verdict or record persistence. The medium-severity direct-IP rule is a genuine counter-signal, not a standalone finding of remote control. No complete host-reputation result is available for the observed IP addresses. No complete contacted-host reputation result was available. Research feeds, malicious-child checks, and engine family labels provide no corroborating malware evidence.
What We Detected
The file is a 1,633-byte DOS batch installer known since May 2023. It has been submitted 7,015 times by 3,605 distinct sources, indicating broad and long-standing circulation.
Threat Behavior
One sandbox run recorded T1562.001, a technique associated with impairing defenses, plus direct connections to several IP addresses. A medium-severity direct-IP rule-based therefore fired, but the sandbox did not return a malicious verdict, create persistence, or record a malicious file it created. The contacted-host reputation check was not completed or saved. No complete contacted-host reputation result was available.
What To Do Now
Only run the script if it came from the expected software vendor or another trusted source, and inspect its short batch contents if practical. Keep security software enabled and avoid running it with administrator privileges unless the installation genuinely requires them.
Where this verdict could be wrong1 caveat
- One of our behaviour rules fired after direct-IP traffic was observed, and the missing contacted-host reputation result means those contacts did not receive a complete saved reputation cross-check.
These are the assessment's weak points. If you believe one applies to your file, report the verdict and we'll re-review it.
- 0/59 antivirus engines reported a malicious or suspicious result.
- The hash has 3,605 unique sources and 7,015 submissions over more than three years.
- No sandbox returned a malicious verdict and no persistence indicators were recorded.
- No MalwareBazaar, CIRCL, or YARAify hit corroborated a threat.
- The sandbox's offensive-technique list includes T1562.001.
- One of our behaviour rules fired at medium severity.
- The missing contacted-host reputation result leaves the observed IP addresses without a complete saved reputation result.
- Batch scripts are unsigned by design, so publisher identity cannot be verified through code signing.
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
- 6spawned processes
- 19network contacts
- 2filesystem & mutex artifacts
Includes 9 mapped techniques and every process, file, registry and network entry.
Show the technical evidenceChapter 04
Technical details
None of the 59 antivirus engines that checked it flag 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.
File fingerprint
- Last analyzed
- Sep 11, 2026, 1:23 PM UTC
- SHA-256
492ee4c16ac45a5483088583c9caa08252d3a1bb3922dbbec834d61673538f17- SHA-1
1495c69946edca474fe30c2b713aacb9f03bbf3a- MD5
eb55aae630088c91b88d2bfae4115ea0
About this file
install_all.bat is a DOS batch file file of 1.6 kB.
- Type and size
- DOS batch file · 1.6 kB
- Signer
- Not applicable
- First seen
- May 18, 2023On VirusTotal.
- Submitted by
- 3,605 distinct sources
First scanned
Includes every engine result (74) 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 install_all.bat safe?
What is install_all.bat?
How many antivirus engines detected install_all.bat?
What is the SHA-256 hash of install_all.bat?
Is it safe to run install_all.bat?
How up to date is this analysis of install_all.bat?
Community
Member reviews and reports for this exact file hash.